Skip to content
cccskills
FreePublished on 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.

The English summary is being prepared. Showing the original description.

sazardev/networking-with-go
See how to install

Files included (1)

  • SKILL.md3.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

analyze-code

Free

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.

The English summary is being prepared. Showing the original description.

sazardev/networking-with-go58Updated Aug 8, 2026

audit-security

Free

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.

The English summary is being prepared. Showing the original description.

sazardev/networking-with-go58Updated Aug 8, 2026

book-flow-analyst

Free

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.

The English summary is being prepared. Showing the original description.

sazardev/networking-with-go58Updated Aug 8, 2026

book-writer

Free

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.

The English summary is being prepared. Showing the original description.

sazardev/networking-with-go58Updated Aug 8, 2026

english-grammar-reviewer

Free

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.

The English summary is being prepared. Showing the original description.

sazardev/networking-with-go58Updated Aug 8, 2026

go-exercise-reviewer

Free

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.

The English summary is being prepared. Showing the original description.

sazardev/networking-with-go58Updated Aug 8, 2026

See all skills by sazardev

Report a problem with this skill