Skip to content
cccskills
FreePublished on GitHub

codebase-design

Design or improve module interfaces using deep-module heuristics. Use when deciding where a seam belongs, reducing caller-facing complexity, improving testability or navigability, or comparing module designs.

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

See how to install

Files included (4)

  • SKILL.md2.6 KB
  • agents/openai.yaml102 B
  • DEEPENING.md2.2 KB
  • DESIGN-IT-TWICE.md2.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Codebase Design

Seek deep modules: substantial useful behavior behind a small, stable interface. Use the concepts below as design lenses, while matching the repository's established domain language.

Working vocabulary

  • Module: a coherent unit with an interface and implementation, at any scale.
  • Interface: everything callers must know, including invariants and failure modes—not just a type signature.
  • Seam: a location where behavior can vary without editing its callers.
  • Adapter: an implementation that connects at a seam.
  • Depth: useful capability relative to interface complexity.
  • Leverage: capability gained by callers; locality: change and knowledge concentrated for maintainers.

Translate these terms to the project's vocabulary when that makes the design clearer. Consistency with the codebase is more valuable than enforcing a private lexicon.

Design workflow

  1. Map representative callers, responsibilities, dependencies, and existing contracts.
  2. Look for coordination or policy that can move behind a smaller interface.
  3. Place seams where variation, ownership, or test isolation justifies them.
  4. Compare alternatives when the choice is consequential.
  5. Validate the candidate with representative caller code and tests.

Heuristics, not laws

  • Reduce methods, parameters, ordering constraints, and configuration callers must understand.
  • Use the deletion test: if removing a module merely spreads its complexity across callers, it was likely earning its keep.
  • Treat pass-through layers skeptically, but keep them when they provide a real compatibility, ownership, policy, or navigation boundary.
  • Introduce dependency seams when actual variation or test isolation repays the indirection; avoid interfaces justified only by hypothetical futures.
  • Prefer tests through observable interfaces, while allowing focused internal tests when they provide cheaper or more precise feedback.
  • Favor explicit dependencies and returned results when they improve control and testability; side effects and internally created dependencies can still be appropriate at well-defined boundaries.

Read DEEPENING.md when consolidating a cluster across dependency boundaries. Read DESIGN-IT-TWICE.md when materially different interface designs can be explored independently.

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

Create or review an AGENTS.md file so coding agents get stable repo-local instructions: environment setup, testing, style, security boundaries, PR policy, and handoff rules. Use when a repo lacks durable agent guidance or when a custom harness needs a predictable context file.

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

stevesolun/ctx588Updated Oct 15, 2026

Recommend the smallest Matt Pocock skill or short skill sequence that fits the user's current goal.

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

stevesolun/ctx588Updated Oct 15, 2026

Decision guide for delegating to caveman-style subagents. Tells the main thread WHEN to spawn `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit), or `cavecrew-reviewer` (diff review) instead of doing the work inline or using vanilla `Explore`. Subagent output is caveman-compressed so the tool-result injected back into main context is ~60% smaller — main context lasts longer across long sessions. Trigger: "delegate to subagent", "use cavecrew", "spawn investigator/builder/reviewer", "save context", "compressed agent output".

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

stevesolun/ctx588Updated Oct 15, 2026

Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.

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

stevesolun/ctx588Updated Oct 15, 2026

Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.

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

stevesolun/ctx588Updated Oct 15, 2026

Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.

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

stevesolun/ctx588Updated Oct 15, 2026

See all skills by stevesolun

Report a problem with this skill