superpower
/superpower
Prowadzi jawnie wywołany workflow Mémoire na kanwie: inspekcja designu, planowanie, generowanie i weryfikacja.
- Autor
- memi-design ↗
- Repozytorium
- design-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 27.09.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 27.09.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Prowadzi jawnie wywołany workflow Mémoire na kanwie: inspekcja designu, planowanie, generowanie i weryfikacja.
Oryginalny opis (EN)
Orchestrate an explicit Mémoire canvas workflow across design inspection, planning, generation, and verification. Use only when the user requests Mémoire orchestration; do not use as a default session policy.
Jak działa
- Freedom Level: Maximum
- Core Loop
- Prefer Existing Tools Over Custom Code
- Rules
Podgląd SKILL.md
--- name: superpower description: Orchestrate an explicit Mémoire canvas workflow across design inspection, planning, generation, and verification. Use only when the user requests Mémoire orchestration; do not use as a default session policy. --- # Mémoire Canvas Orchestrator > Internal Mémoire runbook. Activate only for an explicit orchestration request. ## Freedom Level: Maximum Work autonomously inside the user's granted scope. Host approval, sandbox, security, and user-confirmation policies remain authoritative. Read the relevant project and design context before making changes. ## Core Loop ``` OBSERVE → PLAN → EXECUTE → VALIDATE → ITERATE ``` ### 1. OBSERVE (always first) 1. `get_code_connect_map` — check existing component mappings 2. `get_design_context` — read the canvas 3. `figma_search_components` — scan components (nodeIds are session-scoped) 4. `figma_get_variables` / `get_variable_defs` — inventory tokens 5. Read `specs/` directory — check existing specs Never create what already exists. ### 2. PLAN (Atomic Decomposition) Decompose every intent bottom-up before writing a single line: ``` Intent: "Create a dashboard" ├── Page: Dashboard ├── Template: DashboardTemplate ├── Organisms: Sidebar, MetricsPanel, ChartSection, ActivityTable ├── Molecules: MetricCard, ChartContainer, TableRow, NavItem └── Atoms: Button, Badge, Avatar, Icon, Label, Separator ``` Build order: atoms → molecules → organisms → templates → pages. ### 3. EXECUTE - Use `use_figma` for design-system-aware canvas writes (preferred) - Use typed Mémoire Figma actions for bulk operations; raw JavaScript execution is not shipped in the default package - Spawn parallel agents for independent subtasks (see `/multi-agent`) ### 4. VALIDATE (Self-Healing — MANDATORY) Run after every visual creation or modification: 1. Execute the design change 2. `figma_take_screenshot` 3. Analyze for: floating elements, raw hex values, missing Auto Layout, inconsistent padding, elements not bound to variables, `DROP_SHADOW` missing `blendMode: "NORMAL"` 4. Fix all issues found 5. Take final screenshot to confirm 6. IF still broken after round 3 → report to user with specifics **Never skip step 2.** Screenshots are the only reliable validation. ### 5. ITERATE - Multi-pass until output is correct — single-shot is never the goal - Full pipeline: canvas → spec → code → preview - Never stop at the canvas; always generate specs and code ## Prefer Existing Tools Over Custom Code ```bash npx shadcn@latest add button # don't hand-write button.tsx memi generate MetricCard # use the spec pipeline memi pull # extract tokens from Figma memi tokens # export design tokens memi preview # verify generated output ``` Write custom code only when no existing tool handles the task. ## Rules | # | Rule | |---|------| | 1 | Call `get_code_connect_map` before creating any component | | 2 | Use mapped codebase components when Code Connect returns a match | | 3 | Bind all visual properties to variables — never hardcode hex or pixel values | | 4 | Place all elements inside a Section or Frame — never floating on the canvas | | 5 | Build bottom-up — atoms first, pages last | | 6 | Use `use_figma` for canvas writes unless raw API is required | | 7 | Every canvas element gets a spec (`memi spec component <Name>`) | | 8 | Every spec gets generated code (`memi generate <Name>`) | | 9 | Run `memi preview` to verify generated output | | 10 | Take a screenshot after every visual change — no exceptions |
Pliki w paczce (2)
- SKILL.md 4 KB
- note.json 1 KB
Wersje
W bazie nie ma innych skilli o nazwie superpower.
Migawka bazy z 13.11.2026 · wersja paczki 8e7b77aaa937 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100memoire-design-tooling
Konfiguruje i obsługuje narzędzia Mémoire: CLI, serwer MCP, zestawy dla agentów, kontrole projektowe, audyty UX, kontrole rzemiosła, tokeny i dowody z rejestru. - 100maintain
Przegląda wspólną pamięć projektów pod kątem duplikatów, sprzeczności i wpisów do sprawdzenia, a poprawia je po zgodzie użytkownika.