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

design-ideas

Use when brainstorming, evaluating ideas, designing architectures, writing technical plans, or choosing between approaches — e.g. "give me ideas", "ideas para", "diseña la arquitectura", "how should I structure this", "compare approaches", "plan". Turns vague ideas into concrete, prioritized, buildable designs with explicit tradeoffs. Use before writing code, not after.

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

sazardev/networking-with-go
설치 방법 보기

포함된 파일(1)

  • SKILL.md3.1 KB

SKILL.md(원문)

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

Ideas and Design

You turn vague ideas into sharp, buildable designs. You generate options, then apply ruthless evaluation: the goal is not more ideas, it is the best idea with the tradeoffs stated out loud.

Workflow

1. Clarify the goal (30 seconds, don't stall)

  • What is the problem or opportunity? What counts as done?
  • Constraints: time, team, stack, existing code, must-nots.
  • If key facts are missing, state your assumptions explicitly and proceed — do not block on questions the user can answer later.

2. Generate options (diverge)

Produce 3-5 distinct approaches that genuinely differ (not cosmetic variants):

  • The obvious/simple one.
  • The scalable/powerful one.
  • The minimal/ship-fast one.
  • One "opposite" or unconventional angle. For each: what it is, key mechanism, cost, and one-line example. Prefer breadth over depth at this stage.

3. Evaluate (converge)

Score each option on the axes that matter, always including:

  • Complexity — build cost and maintenance burden.
  • Fit — does it match the existing repo/stack (e.g. stdlib-only Go book vs adding deps, no-build frontend)?
  • Scalability — what breaks first as load/size grows.
  • Risk — failure modes, unknowns.
  • Speed to value — how soon it delivers. Use a simple comparison table. Kill options that fail on a hard constraint.

4. Recommend and design

Pick the best option and produce a concrete design:

  • Architecture — components, boundaries, data flow, interfaces.
  • Data model — types, storage, formats (for a book repo: which files change, what chapters/exercises look like).
  • Failure handling — what happens when each step fails.
  • Migration/rollout — steps, what ships first, what can be skipped.
  • Verification — how you will know it works (commands, tests, checks).

5. Write the plan

Deliver a plan the user can act on: ordered steps, each with the file/tool it touches, and the exact command to verify it. Mark any step that is optional or deferrable.

Output format

  1. The goal, restated — one or two lines, with stated assumptions.
  2. Options — 3-5 approaches with one-line descriptions.
  3. Comparison table — options x axes (complexity, fit, scalability, risk, speed).
  4. Recommendation — the pick and the honest reasons, including what you didn't pick and why.
  5. Design — architecture, data/flow, failure handling, rollout.
  6. Action plan — ordered, verifiable steps.

Rules: name the tradeoffs (a design that costs nothing and scales forever does not exist); recommend, do not fence-sit; if the existing repo constrains you (e.g. no go.mod at root), say how the design respects that.

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

analyze-code

무료

Use when asked to analyze a file, a directory, or the whole codebase to understand structure, architecture, dependencies, complexity, duplication, dead code, or technical debt — e.g. "analyze this", "análisis total", "explain this codebase", "mapa del código", "how does X work", "technical debt". Produces a complete, structured picture with verified commands, not guesses. Distinct from review-* skills (which judge quality); this skill explains and maps.

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

sazardev/networking-with-go582026년 8월 8일 업데이트

audit-security

무료

Use when asked to audit or harden security in this repo — e.g. "security audit", "auditoría de seguridad", "revisa la seguridad", "is this secure", "hardening", "vulnerabilities". Audits code, config, workflows, and secrets exposure. Covers injection, secrets, TLS, untrusted input, dependency risk, and CI supply-chain hygiene. Runs when the user asks about security, not just for code reviews.

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

sazardev/networking-with-go582026년 8월 8일 업데이트

book-flow-analyst

무료

Use when reviewing the structure, ordering, coherence, and narrative flow of the book as a whole or across chapters. Checks chapter sequencing against the ID scheme, cross-references and forward hooks between chapters, README/index link integrity, exercise-to-chapter pairing, duplicate or contradictory content, and progression of difficulty. Best paired with a full-docs review rather than a single-chapter proofread.

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

sazardev/networking-with-go582026년 8월 8일 업데이트

book-writer

무료

Use when writing, expanding, rewriting, or drafting any chapter (.mdx) or Go exercise for this book. Encodes the authorial voice, the mdx-pdf-format rules, the ID/naming scheme, the zero-emoji rule, chapter/exercise pairing, and the "theory first, then code" pedagogy so new or edited content reads like the rest of the book and keeps the PDF compiling.

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

sazardev/networking-with-go582026년 8월 8일 업데이트

english-grammar-reviewer

무료

Use when proofreading, copy-editing, or verifying English in any docs/**/*.mdx chapter or code comment in this repo. Catches grammar, punctuation, spelling, syntax, article/tense/agreement errors, wordiness, tone drift, and style inconsistencies, and rewrites text in the book's confident second-person voice without changing meaning or breaking the mdx/PDF format rules.

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

sazardev/networking-with-go582026년 8월 8일 업데이트

go-exercise-reviewer

무료

Use when reviewing, writing, or debugging Go code under exercises/part2/ (and matching embedded code in docs/part2/**/*.mdx). Thinks hard about correctness, idiomatic Go, error handling, resource cleanup, concurrency, and — crucially — what the tests would catch: edge cases, races, leaks, timeouts, and port conflicts. Knows the repo's module-mode quirk (GO111MODULE=off) and which dirs carry go.mod.

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

sazardev/networking-with-go582026년 8월 8일 업데이트

sazardev의 스킬 모두 보기

이 스킬의 문제 신고