Skip to content

GentBajko/capstone / skills/core

Internal to the capstone suite - carries the shared rules (references/) and scripts every capstone subcommand reads; it exists so npx-skills installs ship them alongside the command skills. Not meant to be invoked directly; when invoked anyway, run references/../scripts/help.sh and output its stdout verbatim.

FileKindSize
SKILL.mdskill md902 B
VERSIONother6 B
references/arch-craft.mdmarkdown6.6 KB
references/code-craft.mdmarkdown9.6 KB
references/core-authoring.mdmarkdown8.7 KB
references/core.mdmarkdown55.5 KB
references/dispatcher.mdmarkdown1.9 KB
references/interview.mdmarkdown17.5 KB
references/logic-craft.mdmarkdown9.5 KB
references/protocols/architecture.mdmarkdown12.2 KB
references/protocols/build.mdmarkdown10.5 KB
references/protocols/doctor.mdmarkdown9.3 KB
references/protocols/edges.mdmarkdown12.6 KB
references/protocols/feature.mdmarkdown5.3 KB
references/protocols/groom.mdmarkdown11.2 KB
references/protocols/implement.mdmarkdown15.2 KB
references/protocols/logic.mdmarkdown10.7 KB
references/protocols/map.mdmarkdown38.5 KB
references/protocols/mockup.mdmarkdown11.0 KB
references/protocols/plan.mdmarkdown9.3 KB
references/protocols/retro.mdmarkdown9.3 KB
references/protocols/review.mdmarkdown10.6 KB
references/protocols/stack.mdmarkdown8.8 KB
references/protocols/standards.mdmarkdown8.5 KB
references/protocols/start.mdmarkdown14.6 KB
references/protocols/uiux.mdmarkdown24.8 KB
references/schema.txtmarkdown11.9 KB
references/standards-inventory.mdmarkdown36.9 KB
references/style.mdmarkdown1.8 KB
references/topics.mdmarkdown21.2 KB
references/uiux-craft.mdmarkdown20.7 KB
references/uiux-inventory.mdmarkdown19.3 KB
scripts/help-hook.shexecutablescript1.5 KB
scripts/help.shexecutablescript6.4 KB
scripts/init-config.shexecutablescript16.3 KB
scripts/lint-sync.shscript133.5 KB
scripts/map-check.shexecutablescript52.8 KB

references/style.md

View on GitHub
# Writing Rules for Generated Docs

The audience is a future Claude session with zero context that must answer
architecture questions without exploring the repo.

## Voice

- Declarative facts only. "Commands are validated in `server/ws.py:88`",
  never "commands should be validated" or "consider validating".
- No recommendations, no judgments, no TODOs, no hedging ("probably",
  "seems to", "appears").
- If something could not be determined, state that explicitly:
  "Retry behavior: not implemented anywhere in `src/net/`."

## Density

- Every claim carries a pointer: `path/to/file.py:123` or `path/to/dir/`.
- Prefer a table for enumerable facts (models, endpoints, dependencies);
  prose only for relationships a table cannot show.
- No filler: delete any sentence that does not help the reader locate or
  understand code. No introductions, no summaries of summaries.
- The index (`<index_file>`) stays under ~2 pages. Topic files have no
  hard cap but must earn their length: if a section repeats the index,
  cut it.
- `changelog.md` is exempt from every length rule: it is never
  condensed, summarized, or pruned.

## Naming

- Use the codebase's own names verbatim (`GenerateMapCommand`, not "the
  map generation command object").
- First mention of a symbol gives its definition site; later mentions do
  not repeat it.

## Structure

- Follow the required section templates in `topics.md` exactly: future
  sessions rely on stable headings to jump to what they need.
- Absent things are facts too: record them where a reader would look
  ("No message queue; all communication is synchronous websocket frames").
- Label shallow coverage: when an area was only skimmed, say so
  ("shallow: static assets, not inventoried") so readers can distinguish
  small-and-boring from not-examined.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall