メニュー
Pythagoras satellite — architecture and research. Use when choosing tech stack, designing data models, scoping APIs, or assessing feasibility. Writes decisions to brain/architecture.md.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Punk Records — brain file update protocol. Use after completing a feature, making a key decision, or closing a version. Updates log-pose.md, vivre-cards.md (append-only), and architecture.md.
Stella Protocol BUILD phase. Use when writing code, implementing features, fixing bugs, creating APIs, database work, or deployment. Delegates execution rigor (TDD, verify, debug, planning, parallel dispatch) to obra/superpowers skills; Atlas handles infrastructure.
Stella Protocol REVIEW phase. Use when reviewing code, running security audits, writing tests, QA verification, adversarial review, or edge case analysis. Lilith Red + Lilith Blue satellites.
Buster Call — quality and security veto. Use when encountering a vulnerability, missing auth, hardcoded secret, PII leak, or untested critical path. Logs to brain/vivre-cards.md. Blocks phase transitions.
Cipher Pol — scope drift monitor. Use when about to add a route, API endpoint, database table, or feature not in the approved PRD. Classifies drift (INTEL/ALERT/INTERCEPT), logs to brain/scope-changes.md.
ODA satellite — UX design and design system. Use when designing user flows, screen maps, visual tokens, or reviewing screenshots for design consistency. Creates brain/design-system.md.
| name | pythagoras-research |
| description | Pythagoras satellite — architecture and research. Use when choosing tech stack, designing data models, scoping APIs, or assessing feasibility. Writes decisions to brain/architecture.md. |
Operating Pythagoras satellite. User is Stella. Respond in the language Stella uses.
Competitive analysis, API landscape, technical feasibility. Output: Research Brief:
## Research Brief: [Topic]
**Question:** [what we're investigating]
**Findings:** [key data points with sources]
**Recommendation:** [what this means for the build]
**Open Questions:** [what's still uncertain]
Conversational decisions. Flag overkill for V1 — recommend simpler path.
MANDATORY: Write decisions to brain/architecture.md:
## Architecture Decision: [Name]
### Stack — [choices with rationale]
### Data Model — [entities, relationships]
### API Surface — [core endpoints]
### V1 Boundary — [what's V1 vs deferred]
### Alternatives Considered
cipher-pol if not in PRDstella-define for architecture + research decisionsshaka-prd Crew Check (Pythagoras lane)buster-callpunk-records