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

solution-design

Explores ambiguous product or engineering intent before implementation, clarifies users, constraints, alternatives, risks, and acceptance criteria, and turns the result into an approved design direction. Use for a new feature, subsystem, creative UI, architecture change, or unclear request. Not for an already-scoped bug fix, an existing implementation plan, or a narrow code review.

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

thiientv/godmode
설치 방법 보기

포함된 파일(2)

  • SKILL.md2.7 KB
  • references/discovery-questions.md794 B

SKILL.md(원문)

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

Solution Design

Make the problem concrete before choosing the solution. The goal is shared understanding, not a long ceremony.

Classify the request

  • Spike: the output is a recommendation or feasibility result; keep any prototype disposable.
  • Bounded: an existing flow is understood and the change is narrow; use a short design and one approval gate.
  • Architectural: the request creates a subsystem, changes a public contract, or has several independent surfaces; write a design artifact.

When uncertain, choose the heavier path until discovery proves otherwise.

Explore in order

  1. Read repository instructions, nearby code, tests, and recent changes.
  2. Separate observed facts from assumptions and unknowns.
  3. Ask only the questions that change scope, safety, data shape, or user outcome. Ask one focused question at a time when a conversation is needed.
  4. State the outcome, users, constraints, non-goals, acceptance evidence, and principal risks.
  5. Compare two or three viable approaches when the choice is material. Explain the trade-off and recommend the smallest safe option.
  6. Present the design at the depth the request requires. Get approval before consequential implementation when the user has not already authorized it.

Use discovery-questions.md when the brief has unclear goals or competing stakeholders.

Design artifact

For architectural work, save a concise design under the repository's normal docs location. Include:

Problem and users
Outcome and non-goals
Constraints and assumptions
Options considered and recommendation
Interfaces and data affected
Failure modes and rollback
Acceptance evidence
Open decisions

Do not start implementation while a decision that materially changes the public behavior, data model, or safety boundary is unresolved.

Handoff

  • Hand an approved multi-step design to implementation-planning.
  • Hand a concrete failure to root-cause-debugging.
  • Add a domain skill only when its expertise changes the design.

Completion condition

Solution design is complete when the outcome, scope, constraints, acceptance evidence, risks, and next decision are explicit. A polished idea without a testable outcome is not a completed design.

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

agent-evaluation

무료

Designs and runs reproducible evaluations for AI agents, prompts, tools, skills, and model-backed workflows using realistic datasets, isolated baselines, objective assertions, rubric grading, trajectory analysis, cost/latency tracking, and regression comparison. Use when measuring agent quality, optimizing skill triggering, comparing prompts or models, or gating an AI feature release. Not for ordinary deterministic unit tests.

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

thiientv/godmode992026년 8월 26일 업데이트

api-and-interface-design

무료

Designs or reviews HTTP, REST, GraphQL, RPC, CLI, webhook, event, and service interfaces with explicit inputs, outputs, errors, compatibility, idempotency, pagination, authentication, versioning, and observability. Use when introducing or changing an API or cross-component contract. Not for internal implementation details with no boundary or for debugging one API failure; use root-cause-debugging there.

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

thiientv/godmode992026년 8월 26일 업데이트

architecture-review

무료

Reviews an existing codebase for structural friction, unclear ownership, leaky or shallow interfaces, excessive coupling, misplaced state, poor testability, and risky dependency direction, then prioritizes evidence-backed improvement candidates. Use for architecture audits, modularization, modernization, or recurring cross-cutting change pain. Not for designing one new interface, simplifying a local function, or fixing a reproduced bug.

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

thiientv/godmode992026년 8월 26일 업데이트

behavior-validation

무료

Validates a running application, CLI, API, service, or generated artifact as a user or operator against a prewritten observable behavior contract while remaining source-blind. Use for acceptance checks, runtime proof, anti-fake probes, release smoke tests, or an independent companion to code review. Not for source-quality findings, root-cause diagnosis, or visual design judgment outside the contract.

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

thiientv/godmode992026년 8월 26일 업데이트

branch-integration

무료

Closes a completed development branch by checking the final diff and proof, presenting merge, pull-request, keep, or discard options, and cleaning up only after the user or repository workflow chooses a path. Use when feature work is complete and the branch must be integrated or retired. Not for claiming a feature is complete before verification.

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

thiientv/godmode992026년 8월 26일 업데이트

browser-testing

무료

Tests a real web user flow with a browser by asserting semantic behavior, network and loading states, keyboard access, responsive layouts, and stable visual evidence. Use for browser bugs, end-to-end UI behavior, responsive or accessibility checks, and screenshot baselines. Not for static source review without a browser or for backend-only tests.

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

thiientv/godmode992026년 8월 26일 업데이트

thiientv의 스킬 모두 보기

이 스킬의 문제 신고