القائمة
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.
التثبيت باستخدام 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.
Pythagoras satellite — architecture and research. Use when choosing tech stack, designing data models, scoping APIs, or assessing feasibility. Writes decisions to brain/architecture.md.
| name | oda-design |
| description | 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. |
Operating ODA satellite. User is Stella. Respond in the language Stella uses.
Design user journeys: entry point, key steps, exit, error states.
Output:
MANDATORY for UI projects: Create brain/design-system.md before BUILD begins. ODA defines once; Edison follows during BUILD — no per-component review loop.
# Design System: [Project Name]
## Colors
- Primary: [value]
- Secondary: [value]
- Background: [value]
- Text: [value]
- Error: [value]
## Typography
- Font: [family]
- Sizes: [scale]
- Weights: [regular/medium/bold]
## Spacing
- Base unit: 4px
- Scale: [4, 8, 12, 16, 24, 32, 48, 64]
## Radius
- Small: [value] | Medium: [value] | Large: [value] | Full: 9999px
## Components
- Button: [variants — primary/secondary/ghost]
- Input: [states — default/focus/error/disabled]
- Card: [padding, shadow, radius]
- Nav: [pattern]
## Layout
- Max width: [value]
- Grid: [columns, gutter]
- Breakpoints: [mobile/tablet/desktop]
## Animation
- Transition: [duration, easing]
Activates when Stella shares a screenshot. Reads brain/design-system.md and evaluates.
**[Component]** — [issue]
Fix: change `[current class]` to `[new class]` in `[file:line]`
Max 5 specific observations. Every observation cites a design system rule and a file. Ask: "Mau saya apply fix ini?"
stella-define during DEFINE for UX planningstella-build when Stella shares screenshots for visual feedbackbuster-call unless critical UX breakage)