From pyrs
Invoke pyrs-foundation first. Produce or update code from a pyramid using incremental test-driven development. Triggered by ::apply P where P is an @-prefixed pyramid reference.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pyrs:pyrs-applyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Before proceeding, invoke the pyrs-foundation skill to load the pyramid system rules — especially the strictness rules. Everything you implement will be scrutinized by auditors and reviewers who enforce those rules strictly.
Before proceeding, invoke the pyrs-foundation skill to load the pyramid system rules — especially the strictness rules. Everything you implement will be scrutinized by auditors and reviewers who enforce those rules strictly.
This skill is activated when the user issues ::apply P where P is an @-prefixed pyramid reference (e.g., ::apply @event-bus or ::apply @./pyramids/event-bus/index.md).
Apply is the only route from concept to code — it handles both building from scratch and updating existing code to match a revised pyramid.
@-prefixed pyramid reference to its pyramid file (see Pyramid Identifiers in _foundation.md)After apply mutates code for target P, check whether a sibling diff.md exists for that target either:
If yes, run a same-target ::diff P refresh before returning final output.
diff.md based on remaining discrepancies; apply does not directly edit diff.md itself.These will be enforced by future audits and reviews. Violations are failures.
When P references children or See Also siblings that are not yet built or complete:
// PYRS_TODO: ./pyramids/[pyramid file or directory]PYRS_TODO placeholders — instead, note unbuilt dependencies in the pyramid itselfMark generated code and tests with // PYRS: P comments (using P's identifier-form @ reference) so the pyramid-to-code mapping is clear. Use the comment syntax appropriate for the language (#, //, /* */, etc.).
// PYRS: @event-bus.actions), not file pathsPYRS comments from prior runs should remain accurateThese comments help ::diff trace code back to its governing pyramid and make audits easier.
Exception: if P (or any of its ancestors) has a Constraint prohibiting code markers, skip provenance comments entirely. This exception is inherited — a parent's opt-out applies to all its descendants, but does not affect other branches. This is common for meta pyramid repos where the codebase is not owned by the pyramid author.
Your code will be audited against P. Auditors will check:
PYRS_TODO placeholders are accurate for the current state of children and See Also dependencies (unless P's Constraints prohibit code markers)PYRS provenance comments are present and accurate (unless P's Constraints prohibit code markers)Write code that cleanly maps to P's concepts. When an auditor reads P and then your code, the alignment should be obvious.
npx claudepluginhub zachbutton/pyrs --plugin pyrsEstablishes Python 3.11+ engineering standards: SOLID principles, strict typing policy, pytest testing defaults, ruff linting, uv tooling, code smell detection. Auto-activates on Python tasks.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.