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/schema.txt

View on GitHub
# The output schema: one record per kind of file capstone writes under a
# docs area, in the machine-readable form the gate can read without a
# model.
#
# skills/core/scripts/map-check.sh reads this file at runtime and keeps
# no copy of it. references/topics.md and the protocol files under
# references/protocols/ carry the prose a model follows while writing a
# page; lint-sync checks 15, 20 and 21 assert that the prose and this
# file still say the same thing, so changing one alone turns the lint
# red.
#
# A change here reaches pages already on disk the ordinary way. Their
# `capstone_version` now sits below the plugin's, part 1 calls them
# "written by an older capstone", and the next `map` run rewrites them
# against the current template.
#
# Format. One record per output type. Records are separated by a blank
# line, fields are one per line, and a line whose first character is `#`
# is a comment. The fields:
#
#   type      <id>                  the record's name, unique
#   match     <glob>                a path relative to the docs dir, as a
#                                   shell glob; a record may carry more
#                                   than one
#   keys      <k> <k> ...           frontmatter keys required inside git
#   keys!     <k> <k> ...           frontmatter keys required always
#   opt       <k> <k> ...           keys from `keys` that a page carrying
#                                   no `paths_covered` does not owe
#   head      <H>|<H>|...           required `## ` headings, in this order
#   table     <Heading>:<C>|<C>     the first table under `## <Heading>`
#                                   must carry these columns
#   subtable  <Heading>:<n>:<C>|<C> every heading at level `<n>` under
#                                   `## <Heading>` must carry a table
#                                   with these columns
#   from      <file>|<section>      the protocol section `head` was
#                                   copied from; lint check 20 reads it
#
# Matching. The first `match` glob that fits the path decides the
# record, and records are tried in file order, so specific patterns sit
# above general ones. The last record is a catch-all: every markdown
# page under a docs area owes `generated_date` even when nothing more
# specific claims it. The resolved index file is looked up by the `index`
# record whatever `index_file` names it, so a docs area that renames its
# index still gets the index rules rather than a chapter's.
#
# Headings. `head` is an ordered sequence. A heading that is not there is
# the finding `## <H>`. A heading that sits ahead of one that should
# precede it is `## <H> out of order (before ## <Prev>)`. Extra `## `
# headings are never a finding, so a chapter may carry sections beyond
# the ones the template names.
#
# Tables. The heading and the level are split off a `table` or
# `subtable` value at its first colon, so a heading holding a colon
# cannot be named by either field; no template heading holds one.
# Columns are matched by lowercased header name, never by position, and
# extra columns are allowed. A missing column is the finding
# `table <Heading> missing <Column>`. A heading whose `head`
# entry is itself absent reports the heading alone and no columns, so one
# gap is one finding. `table` says nothing about a section that carries
# no table: topics.md tells a deep-dive to write "None found" plus where
# it looked, so an empty section is the sanctioned answer. `subtable` is
# strict the other way, because topics.md gives a `### <Entity>` section
# no such out - it holds a field table or it holds nothing anyone can
# read. All of these land in part 8's missing-headings column and count
# toward the stale verdict.
#
# Waivers. `mode: prescriptive` waives `keys` outright: a design written
# before the code has no commit to stamp. Outside git `keys` is waived
# for the same reason, and `keys!` is owed under both. `opt` waives its
# keys on a page with no `paths_covered`, which is how an interview's
# output and the same file written by extraction are told apart.

type    index
match   00-index.md
# core-authoring.md's Index maintenance rule: the index carries no
# stamps, `generated_date` included, because freshness lives in each
# chapter's own frontmatter and a second copy would only drift. It has
# no required headings either. Secret-shaped strings are still scanned,
# the way they are in every file.

type    logic-scenario
match   logic/*.md
keys    generated_at_commit content_hash paths_covered
keys!   generated_date
opt     generated_at_commit content_hash paths_covered
head    Trigger & preconditions|Steps|Branches|Unhappy paths|State transitions|Invariants|Outcomes & side effects|Dimensions not in play
from    logic.md|Phase B

type    mockup-readme
match   mockup/README.md
keys!   generated_date
# Phase E's tail requires a product brief and three tables, Screens,
# Journeys and Scenarios for `logic`. It names no `## ` heading for any
# of them, so there is nothing here to pin yet; spelling the headings out
# is a mockup.md change, and the record gains a `head` when that lands.

type    mockup-screen
match   mockup/[0-9][0-9]-*.md
keys!   generated_date
head    Layout|Elements|States
from    mockup.md|Phase E

type    uiux-readme
match   uiux/README.md
keys!   generated_date
# Phase E asks this file for one table, design chapter to mockup screen
# to logic scenarios, under no named heading.

type    uiux-direction
match   uiux/01-direction.md
keys    generated_at_commit content_hash paths_covered
keys!   generated_date
opt     generated_at_commit content_hash paths_covered
# Phase E describes the design read, the mode map and the four contract
# blocks in prose and names no `## ` heading, so this record pins the
# stamps only.

type    uiux-system
match   uiux/02-system.md
keys    generated_at_commit content_hash paths_covered
keys!   generated_date
opt     generated_at_commit content_hash paths_covered
head    Implementation constraints|Assets
table   Assets:Asset|File|Source|Status
from    uiux.md|Phase E
# The Assets table is the brand-asset manifest uiux-inventory.md's S15
# fills and `build` consumes: a row whose `Status` is `awaited` stops
# the build rather than shipping a placeholder, so the column is pinned
# here the way the interfaces tables' are.

type    uiux-experience
match   uiux/03-experience.md
keys    generated_at_commit content_hash paths_covered
keys!   generated_date
opt     generated_at_commit content_hash paths_covered
head    Not in play
from    uiux.md|Phase E
# Phase E lists the experience rules themselves in prose and names no
# `## ` heading for them; the closing section is the one it does name.

type    uiux-screen
match   uiux/screens/*.md
keys    generated_at_commit content_hash paths_covered
keys!   generated_date
opt     generated_at_commit content_hash paths_covered
head    Mode & job|Composition|States|Motion|Copy|Not in play
from    uiux.md|Phase E

type    chapter-architecture
match   [0-9][0-9]-architecture.md
match   [0-9][0-9]-architecture-*.md
keys    generated_at_commit content_hash paths_covered
keys!   generated_date
head    Layers|Module boundaries|Entry points|Communication|Composition|Frontend
from    topics.md|architecture.md

type    chapter-models
match   [0-9][0-9]-models.md
match   [0-9][0-9]-models-*.md
keys    generated_at_commit content_hash paths_covered
keys!   generated_date
head    Entities|Fields and types|Relationships|Boundaries|Validation|Schema
subtable Fields and types:3:Field|Type|Required
from    topics.md|models.md
# The Entities table's columns are prose in topics.md ("name, definition
# site, storage, one-line purpose"), not literal header text, and the
# chapters capstone has written spell the first column both `Name` and
# `Entity`. Pinning them is a topics.md change first.

type    chapter-conventions
match   [0-9][0-9]-conventions.md
match   [0-9][0-9]-conventions-*.md
keys    generated_at_commit content_hash paths_covered
keys!   generated_date
head    Paradigm|Typing|Error handling|Dependency injection
from    topics.md|conventions.md

type    chapter-data-flow
match   [0-9][0-9]-data-flow.md
match   [0-9][0-9]-data-flow-*.md
keys    generated_at_commit content_hash paths_covered
keys!   generated_date
head    Lifecycles|State|Side-effect boundaries|Failure paths
from    topics.md|data-flow.md

type    chapter-dependencies
match   [0-9][0-9]-dependencies.md
match   [0-9][0-9]-dependencies-*.md
keys    generated_at_commit content_hash paths_covered
keys!   generated_date
head    Dev and tooling|External services
from    topics.md|dependencies.md

type    chapter-testing
match   [0-9][0-9]-testing.md
match   [0-9][0-9]-testing-*.md
keys    generated_at_commit content_hash paths_covered
keys!   generated_date
head    Layout|Doubles|Coverage shape
from    topics.md|testing.md

type    chapter-operations
match   [0-9][0-9]-operations.md
match   [0-9][0-9]-operations-*.md
keys    generated_at_commit content_hash paths_covered
keys!   generated_date
head    Processes|Configuration|Infrastructure|Developer workflow
from    topics.md|operations.md

type    chapter-glossary
match   [0-9][0-9]-glossary.md
match   [0-9][0-9]-glossary-*.md
keys    generated_at_commit content_hash paths_covered
keys!   generated_date
head    Concepts
from    topics.md|glossary.md

type    chapter-interfaces
match   [0-9][0-9]-interfaces.md
match   [0-9][0-9]-interfaces-*.md
keys    generated_at_commit content_hash paths_covered
keys!   generated_date known_as
head    Produces|Consumes
table   Produces:Kind|Name|To|Site
table   Consumes:Kind|Name|From|Site
from    topics.md|interfaces.md
# `known_as` sits under `keys!` because topics.md makes the key owed
# whatever the mode and inside git or out: `known_as: []` is a recorded
# observation, and a scalar value makes quarry register no alias at all.
# The chapter's payload sections get no `subtable`, because topics.md
# gives a `### <Name>` section two legal forms and `Model: <Entity>`
# carries no table; part 8 reads them with the rule that knows both.

type    standards
match   standards.md
keys!   generated_date
head    Typing|Libraries vs reinventing|Paradigm|Error handling|Organization|Documentation|Testing|Tooling|CI gates|Security|Logging and privacy|API conventions|Accessibility|Performance budgets|Versioning and release|Process|Agent rules|Not in play
from    standards-inventory.md|3. The domains
# standards.md carries no `paths_covered` by design, per
# protocols/standards.md: it records decisions rather than observations,
# so no glob makes it stale. The seventeen domains and their order are
# references/standards-inventory.md's §3, which is why `from` names a
# reference rather than a protocol. Every heading is written even when
# the domain was ruled out - the section holds one sentence pointing at
# `Not in play` - so a missing one is a real gap rather than a project
# that had nothing to say.

type    implementation
match   implementation.md
keys!   generated_date

type    review
match   review.md
match   be-review.md
match   fe-review.md
keys!   generated_date
# The review outputs are gitignored, and map-check's skip list drops
# them before any record is looked up. The record is what a committed
# one would be held to if the skip list ever lets it through.

type    questionnaire
match   questionnaires/*.md
keys!   generated_date
head    Purpose|Context|How to answer|Questions|Anything else?
# The send core.md's Questionnaires section governs. It is committed
# rather than local working state, so the gate holds it to its five
# sections the way it holds a logic scenario to its eight; a send
# missing `## How to answer` is the one that comes back late or not at
# all. There is no `from` line because the section list lives in
# core.md, which is neither a protocol nor an inventory and so is not a
# path check 20 resolves; lint check 25 compares the two lists instead.

type    page
match   *
keys!   generated_date
# The catch-all. Any other markdown page a docs area carries still owes
# a date, which is what part 8 asked of every unclassified file before
# this file existed.
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