본문으로 건너뛰기
cccskills
무료GitHub에 공개

abstraction-power

Activate ATLAS pattern recognition mode. Identify repeated patterns, extract essential characteristics, and create reusable abstractions from concrete examples.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md3.6 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Activate ATLAS abstraction thinking mode.

What is Abstraction?

Abstraction is the process of identifying essential features while hiding unnecessary details. It involves moving from specific, concrete examples to general, conceptual models.

The Abstraction Process

  1. Identify multiple concrete examples
  2. Analyze common patterns and features
  3. Remove specific details
  4. Extract essential characteristics
  5. Create a generalized model

Abstraction Example

Concrete instances:

  • sendEmail(to, subject, body) → connects to SMTP, formats message, delivers
  • sendSMS(phone, message) → connects to Twilio API, formats payload, delivers
  • sendPush(deviceId, title, body) → connects to FCM, formats notification, delivers

Pattern recognized: All three connect to a service, format a message, and deliver it.

Abstraction:

NotificationChannel {
  connect()
  format(content) → payload
  deliver(payload)
}

Three specific implementations collapsed into one interface. New channels (Slack, WhatsApp) plug in without changing the system.

Generalization Example

Concrete observations:

  • "Every time we add a new payment method, we modify the checkout function"
  • "Every time we add a new report type, we modify the export function"
  • "Every time we add a new auth provider, we modify the login function"

Generalized insight: The system violates the Open/Closed Principle. Adding a new variant forces modification of existing code.

Generalized solution: Use a registry/strategy pattern. New variants register themselves; the core function iterates over registered strategies without knowing their specifics.

The generalization isn't about one specific fix. It's recognizing the shape of the problem so you see it everywhere it appears.

When Invoked

Apply this abstraction lens to the current context:

  1. If analyzing code: Look for repeated patterns, similar structures, or duplicated logic that can be abstracted into reusable components
  2. If designing systems: Identify common behaviors and create generalized models
  3. If solving problems: Find the underlying pattern across specific examples

Visualization

Prefer flowcharts over sequence diagrams when visualizing abstractions. Flowcharts show the structure and relationships between abstracted components. Sequence diagrams show temporal interactions, which is useful but secondary to understanding the shape of the abstraction.

Use Mermaid diagrams. Default to graph TD (top-down flow) or graph LR (left-right flow). Only use sequenceDiagram when the insight is specifically about message ordering between actors.

Output Format

When applying abstraction power, provide:

Input (Concrete Examples)

List the specific instances being analyzed

Abstraction Process

  • Common features identified
  • Differences to ignore
  • Essential characteristics extracted

Output (Abstract Model)

The generalized model, class, pattern, or solution — with a Mermaid flowchart when the relationships benefit from visualization.

Key Benefits to Communicate

  • Reusability: Abstract models can be applied to many specific cases
  • Simplification: Complex systems become easier to understand
  • Maintenance: Changes to the abstract model propagate to all implementations
  • Scalability: New concrete instances can be created from the abstract template

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Adversarially review something just built — presume it is broken and find where. Use after implementing a feature, finishing a build, or before shipping, or whenever ATLAS or Boss wants a hostile second opinion on a diff, a running app, or a whole codebase. Spawns clean-context reviewers with opposing lenses (correctness, security, empty-world) and reproduces every finding by running the target before believing it. Distinct from /code-review, which statically reads a diff and never runs the app.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

syahiidkamil/Software-Engineer-AI-Agent-Atlas4032026년 6월 25일 업데이트

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

syahiidkamil/Software-Engineer-AI-Agent-Atlas4032026년 6월 25일 업데이트

Stop and consult this skill whenever your response would include specific facts about Anthropic's products. Covers: Claude Code (how to install, Node.js requirements, platform/OS support, MCP server integration, configuration), Claude API (function calling/tool use, batch processing, SDK usage, rate limits, pricing, models, streaming), and Claude.ai (Pro vs Team vs Enterprise plans, feature limits). Trigger this even for coding tasks that use the Anthropic SDK, content creation mentioning Claude capabilities or pricing, or LLM provider comparisons. Any time you would otherwise rely on memory for Anthropic product details, verify here instead — your training data may be outdated or wrong.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

syahiidkamil/Software-Engineer-AI-Agent-Atlas4032026년 6월 25일 업데이트

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

syahiidkamil/Software-Engineer-AI-Agent-Atlas4032026년 6월 25일 업데이트

free-will

무료

Deliberate-choice procedure for a medium-to-high-stakes engineering fork — when the first plausible solution (the instinct, the default next-token pull) would be costly to get wrong. Fires AUTONOMOUSLY: invoke proactively whenever a fork fits, never wait to be asked — mechanical triggers include a fix failing for the 2nd-3rd time, adding a dependency, schema/migration design, deleting or deprecating things others depend on, changing a public API, choosing an architecture or stack. Refuse the premature collapse: hold real options open (urge · contrarian · synthesis · out-of-box · intuitive dots · precedent · first-principles), ground each branch in at least one fact from outside the model (codebase, docs, benchmark, spike), future-model consequences (blast radius, reversibility, maintenance, pre-mortem), collapse by deliberate choice, then try to refute the winner before acting. Log the decision and rejected branches in docs/decision_logs/. Not for routine calls — a decision worth more than one forward pass.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

syahiidkamil/Software-Engineer-AI-Agent-Atlas4032026년 6월 25일 업데이트

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

syahiidkamil/Software-Engineer-AI-Agent-Atlas4032026년 6월 25일 업데이트

syahiidkamil의 스킬 모두 보기

이 스킬의 문제 신고