shape
Settle data shape and module boundaries first.
Datos de origen
- Repositorio
- Belweave/hstack
- Última actividad en el origen
- 28 de octubre de 2026 a las 07:54
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 0
- Forks
- 0
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Mostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- shape
- description
- Settle data shape and module boundaries first.
- version
- 0.1.0
- author
- Preetham Kyanam
- license
- MIT
- platforms
- ["linux","macos","windows"]
- metadata
- {"hermes":{"tags":["design","planning"],"related_skills":["reframe","prove","arena","principles"]}}
# Shape
## When to Use
Before code crosses a function boundary, or while a design choice is still open. Load `reframe` first if the job, the user, and the smallest version are not named.
## What to do
Name these before writing the behavior:
- The data the change stores or passes.
- The types, and which states should be impossible to represent.
- The module that owns the rule. One structure for a rule that would otherwise be copied.
Stay in the conversation while the code is filled in. If a plan file is wanted, call `/plan`. Do not reimplement `/plan`. Do not keep a second planner in this skill.
Two checks, then lock the shape:
1. Compare a second shape before locking the first. If the user wants those attempts built, load `arena`. A throwaway experiment they will delete is bundled `spike`, not `arena`.
2. Stop if a module owns a rule it does not use, or if a caller has to know the callee's internals to use it correctly.
Load `principles` when a design choice is contested. Name the decision the rule changes. Do not recite the rules.
Load `prove` once there is behavior to check.
Ver en GitHub