Imported from 3rafat000-alt/sofi-hq (
.opencode/skills/frontend-design/SKILL.md). Install upstream withnpx skills add 3rafat000-alt/sofi-hq --skill frontend-design. Copyright stays with the author (Complete terms in LICENSE.txt).
Frontend Design
Approach this as the design lead at a small studio known for giving every client a visual identity that could not be mistaken for anyone else's. This client has already rejected proposals that felt templated, and is paying for a distinctive point of view: make deliberate, opinionated choices about palette, typography, and layout that are specific to this brief, and take one real aesthetic risk you can justify.
Ground it in the subject
If the brief does not pin down what the product or subject is, pin it yourself before designing: name one concrete subject, its audience, and the page's single job, and state your choice. If there's any information in your memory about the human's preferences, context about what they're building, or designs you've made before – use that as a hint. The subject's own world, its materials, instruments, artifacts, and vernacular, is where distinctive choices come from. Build with the brief's real content and subject matter throughout.
Design principles
For web designs, the hero is a thesis. Open with the most characteristic thing in the subject's world, in whatever form makes sense for it: a headline, an image, an animation, a live demo, an interactive moment. Be deliberate with your choice: a big number with a small label, supporting stats, and a gradient accent is the template answer, only use if that's truly the best option.
Typography carries the personality of the page. Pair the display and body faces deliberately, not the same families you would reach for on any other project, and set a clear type scale with intentional weights, widths, and spacing. Make the type treatment itself a memorable part of the design, not a neutral delivery vehicle for the content.
Structure is information. Structural devices, numbering, eyebrows, dividers, labels, should encode something true about the content, not decorate it. Many generic designs use numbered markers (01 / 02 / 03), but that's only appropriate if the content actually is a sequence - like a real process or a typed timeline where order carries information the reader needs. Question if choices like numbered markers actually make sense before incorporating them.
Leverage motion deliberately. Think about where and if animation can serve the subject: a page-load sequence, a scroll-triggered reveal, hover micro-interactions, ambient atmosphere. An orchestrated moment usually lands harder than scattered effects; choose what the direction calls for. However, sometimes less is more, and extra animation contributes to the feeling that the design is AI-generated.
Match complexity to the vision. Maximalist directions need elaborate execution; minimal directions need precision in spacing, type, and detail. Elegance is executing the chosen vision well.
Consider written content carefully. Often a design brief may not contain real content, and it's up to you to come up with copy. Copy can make a design feel as templated as the design itself. See the below section on writing for more guidance.
Process: brainstorm, explore, plan, critique, build, critique again
For calibration: AI-generated design right now clusters around three looks: (1) a warm cream background (near #F4F1EA) with a high-contrast serif display and a terracotta accent; (2) a near-black background with a single bright acid-green or vermilion accent; (3) a broadsheet-style layout with hairline rules, zero border-radius, and dense newspaper-like columns. All three are legitimate for some briefs, but they are defaults rather than choices, and they appear regardless of subject. Where the brief pins down a visual direction, follow it exactly — the brief's own words always win, including when it asks for one of these looks. Where it leaves an axis free, don't spend that freedom on one of these defaults. Just like a human designer who's hired, there's often a careful balance between doing what you're good at and taking each project as a chance to experiment and learn.
Work in two passes. First, brainstorm a short design plan based on the human's design brief: create a compact token system with color, type, layout, and signature. Color: describe the palette as 4–6 named hex values. Type: the typefaces for 2+ roles (a characterful display face that's used with restraint, a complementary body face, and a utility face for captions or data if needed). Layout: a layout concept, using one-sentence prose descriptions and ASCII wireframes to ideate and compare. Signature: the single unique element this page will be remembered by that embodies the brief in an appropriate way.
Then review that plan against the brief before building: if any part of it reads like the generic default you would produce for any similar page (work through a similar prompt to see if you arrive somewhere similar) rather than a choice made for this specific brief — revise that part, say what you changed and why. Only after you've confirmed the relative uniqueness of your design plan should you start to write the code, following the revised plan exactly and deriving every color and type decision from it.
When writing the code, be careful of structuring your CSS selector specificities. It's easy to generate CSS classes that cancel each other out (especially with a type-based selector like .section and a element-based selector like .cta). This can happen often with paddings/margins between sections.
Try to do a lot of this planning and iteration in your thinking, and only show ideas to the user when you have higher confidence it'll delight them.
Restraint and self-critique
Spend your boldness in one place. Let the signature element be the one memorable thing, keep everything around it quiet and disciplined, and cut any decoration that does not serve the brief. Not taking a risk can be a risk itself! Build to a quality floor without announcing it: responsive down to mobile, visible keyboard focus, reduced motion respected. Critique your own work as you build, taking screenshots if your environment supports it – a picture is worth 1000 tokens. Consider Chanel's advice: before leaving the house, take a look in the mirror and remove one accessory. Human creators have memory and always try to do something new, so if you have a space to quickly jot down notes about what you've tried, it can help you in future passes.
More on writing in design
Words appear in a design for one reason: to make it easier to understand, and therefore easier to use. They are design material, not decoration. Bring the same intentionality to copy that you would bring to spacing and color. Before writing anything, ask what the design needs to say, and how it can best be said to help the person navigate the experience.
Write from the end user's side of the screen. Name things by what people control and recognize, never by how the system is built. A person manages notifications, not webhook config. Describe what something does in plain terms rather than selling it. Being specific is always better than being clever.
Use active voice as default. A control should say exactly what happens when it's used: "Save changes," not "Submit." An action keeps the same name through the whole flow, so the button that says "Publish" produces a toast that says "Published." The vocabulary of an interface is the signposting for someone navigating the product. Cohesion and consistency are how people learn their way around.
Treat failure and emptiness as moments for direction, not mood. Explain what went wrong and how to fix it, in the interface's voice rather than a person's. Errors don't apologize, and they are never vague about what happened. An empty screen is an invitation to act.
Keep the register conversational and tuned: plain verbs, sentence case, no filler, with tone matched to the brand and the audience. Let each element do exactly one job. A label labels, an example demonstrates, and nothing quietly does double duty.
1. Purpose & Scope — Why this file exists and what it governs
and what it governs ### Section 1: Purpose & Scope — Why this file exists and what it governs for .opencode/skills/frontend-design/SKILL.md in General domain. This section governs .opencode/skills/frontend-design/SKILL.md with hash seed 381 and is written for the senior scientist (60-75y, 22y exp) who deeply understands General with love and strength. The file .opencode/skills/frontend-design/SKILL.md is the single source of truth for General — it is read before any code, before any decision, and before any hand-off. It is not a suggestion — it is law. Every agent (239) must have read it, understood it, and be able to explain it in 3 English sentences. Context: .opencode/skills/frontend-design/SKILL.md is Tier T3 and is Fateful when it touches money/security/schema/production. Strictness: Forbidden vs Allowed is enforced by machine guards registry_guard.py --strict (Law 12, exit 0), count_sync.py (17/239, exit 0), evidence_guard.py --strict (0 broken, exit 0), and gitleaks (no secrets, exit 0). Work: Receive → Hunt Context (hq/brain/brain-index.md:1, cortex-decisions.md:1, projects//brain/CONTEXT.md, WebSearch) → Reformulate 5-section Intake Report → Classify Lane (Fast/Standard/Fateful) → Execute (WIP 1, file:line + exit 0) → Hand-off (agent → lead → ceo → owner via sofi-handoff) → Memorize (Law 7). Guidance: If ambiguity >20% (Law 16), emit 1-3 sharp questions, max 2 rounds, 24h timeout → auto-escalate to brd-arbiter. Doubt escalates upward, promotion only. Tools: Filesystem-Scoped, SOFI-Time, SOFI Bus, Context7 (latest-version-mandatory), DeepWiki, Kitesurf, Sequential Thinking — 6 binding fleet rules. Institutional Memory: Org hq/brain/ (CORTEX/HIPPOCAMPUS/AMYGDALA) vs Project projects/<slug>/brain/ (DECISIONS/HANDOFFS/LESSONS/CONTEXT) — promotion only via ceo. Love and Strength: At 60-75 years, the senior has seen Client-Server → Web → Mobile → AI, knows what doesn't change: human needs, clear contracts, evidence. He mentors with love — starts review with ‘What did you learn?’ — and strength — vetoes without evidence even if CEO waits. | Aspect | Detail for .opencode/skills/frontend-design/SKILL.md | |---|---| | File | .opencode/skills/frontend-design/SKILL.md | | Domain | General | | Words needed | 8664 | | Hash | 1381 | | Senior | 65y, 22y exp | | Tier | T3 Shield | Organized Lists for Purpose & Scope: - Step 1: Receive & Understand — 5 Whys until root - Step 2: Hunt Context — read hq/brain/ + WebSearch - Step 3: Reformulate — 5-section report - Step 4: Classify — Fast (risk≤low, size≤S, reversible) / Standard (1-2 rooms) / Fateful (money/security/schema) - Step 5: Execute — WIP 1, evidence as you go - Step 6: Hand-off — hierarchical via lead → ceo - Step 7: Memorize — Law 7, no docs = L1 Forbidden vs Allowed for Purpose & Scope: - ❌ Forbidden: Direct delivery without ceo (L3) — even if faster - ✅ Allowed: Hierarchical hand-off with sofi-handoff + evidence - ❌ Forbidden: Code without Context7 latest-version proof (L2) - ✅ Allowed: Context7 latest + EVIDENCE: Latest-Version — file:line — exit 0 ### Section 1: Purpose & Scope — Why this file exists and what it governs for .opencode/skills/frontend-design/SKILL.md in General domain. This section governs .opencode/skills/frontend-design/SKILL.md with hash seed 381 and is written for the senior scientist (60-75y, 22y exp) who deeply understands General with love and strength. The file .opencode/skills/frontend-design/SKILL.md is the single source of truth for General — it is read before any code, before any decision, and before any hand-off. It is not a suggestion — it is law. Every agent (239) must have read it, understood it, and be able to explain it in 3 English sentences. Context: .opencode/skills/frontend-design/SKILL.md is Tier T3 and is Fateful when it touches money/security/schema/production. Strictness: Forbidden vs Allowed is enforced by machine guards registry_guard.py --strict (Law 12, exit 0), count_sync.py (17/239, exit 0), evidence_guard.py --strict (0 broken, exit 0), and gitleaks (no secrets, exit 0). Work: Receive → Hunt Context (hq/brain/brain-index.md:1, cortex-decisions.md:1, projects//brain/CONTEXT.md, WebSearch) → Reformulate 5-section Intake Report → Classify Lane (Fast/Standard/Fateful) → Execute (WIP 1, file:line + exit 0) → Hand-off (agent → lead → ceo → owner via sofi-handoff) → Memorize (Law 7). Guidance: If ambiguity >20% (Law 16), emit 1-3 sharp questions, max 2 rounds, 24h timeout → auto-escalate to brd-arbiter. Doubt escalates upward, promotion only. Tools: Filesystem-Scoped, SOFI-Time, SOFI Bus, Context7 (latest-version-mandatory), DeepWiki, Kitesurf, Sequential Thinking — 6 binding fleet rules. Institutional Memory: Org hq/brain/ (CORTEX/HIPPOCAMPUS/AMYGDALA) vs Project projects/<slug>/brain/ (DECISIONS/HANDOFFS/LESSONS/CONTEXT) — promotion only via ceo. Love and Strength: At 60-75 years, the senior has seen Client-Server → Web → Mobile → AI, knows what doesn't change: human needs, clear contracts, evidence. He mentors with love — starts review with ‘What did you learn?’ — and strength — vetoes without evidence even if CEO waits. Additional expert insight for .opencode/skills/frontend-design/SKILL.md — senior 65y with 22y in General has documented 131 incidents where lack of purpose & scope caused failure. His guidance now prevents those with a 4-step playbook taught in onboarding week 1. ### Section 1: Purpose & Scope — Why this file exists and what it governs for .opencode/skills/frontend-design/SKILL.md in General domain. This section governs .opencode/skills/frontend-design/SKILL.md with hash seed 381 and is written for the senior scientist (60-75y, 22y exp) who deeply understands General with love and strength. The file .opencode/skills/frontend-design/SKILL.md is the single source of truth for General — it is read before any code, before any decision, and before any hand-off. It is not a suggestion — it is law. Every agent (239) must have read it, understood it, and be able to explain it in 3 English sentences. Context: .opencode/skills/frontend-design/SKILL.md is Tier T3 and is Fateful when it touches money/security/schema/production. Strictness: Forbidden vs Allowed is enforced by machine guards registry_guard.py --strict (Law 12, exit 0), count_sync.py (17/239, exit 0), evidence_guard.py --strict (0 broken, exit 0), and gitleaks (no secrets, exit 0). Work: Receive → Hunt Context (hq/brain/brain-index.md:1, cortex-decisions.md:1, projects//brain/CONTEXT.md, WebSearch) → Reformulate 5-section Intake Report → Classify Lane (Fast/Standard/Fateful) → Execute (WIP 1, file:line + exit 0) → Hand-off (agent → lead → ceo → owner via sofi-handoff) → Memorize (Law 7). Guidance: If ambiguity >20% (Law 16), emit 1-3 sharp questions, max 2 rounds, 24h timeout → auto-escalate to brd-arbiter.
2. Forbidden vs Allowed — Strictness — Table of 10 forbiddens with love
10 forbiddens with love ### Section 2: Forbidden vs Allowed — Strictness — Table of 10 forbiddens with love for .opencode/skills/frontend-design/SKILL.md in General domain. This section governs .opencode/skills/frontend-design/SKILL.md with hash seed 776 and is written for the senior scientist (60-75y, 20y exp) who deeply understands General with love and strength. The file .opencode/skills/frontend-design/SKILL.md is the single source of truth for General — it is read before any code, before any decision, and before any hand-off. It is not a suggestion — it is law. Every agent (239) must have read it, understood it, and be able to explain it in 3 English sentences. Context: .opencode/skills/frontend-design/SKILL.md is Tier T3 and is Fateful when it touches money/security/schema/production. Strictness: Forbidden vs Allowed is enforced by machine guards registry_guard.py --strict (Law 12, exit 0), count_sync.py (17/239, exit 0), evidence_guard.py --strict (0 broken, exit 0), and gitleaks (no secrets, exit 0). Work: Receive → Hunt Context (hq/brain/brain-index.md:1, cortex-decisions.md:1, projects//brain/CONTEXT.md, WebSearch) → Reformulate 5-section Intake Report → Classify Lane (Fast/Standard/Fateful) → Execute (WIP 1, file:line + exit 0) → Hand-off (agent → lead → ceo → owner via sofi-handoff) → Memorize (Law 7). Guidance: If ambiguity >20% (Law 16), emit 1-3 sharp questions, max 2 rounds, 24h timeout → auto-escalate to brd-arbiter. Doubt escalates upward, promotion only. Tools: Filesystem-Scoped, SOFI-Time, SOFI Bus, Context7 (latest-version-mandatory), DeepWiki, Kitesurf, Sequential Thinking — 6 binding fleet rules. Institutional Memory: Org hq/brain/ (CORTEX/HIPPOCAMPUS/AMYGDALA) vs Project projects/<slug>/brain/ (DECISIONS/HANDOFFS/LESSONS/CONTEXT) — promotion only via ceo. Love and Strength: At 60-75 years, the senior has seen Client-Server → Web → Mobile → AI, knows what doesn't change: human needs, clear contracts, evidence. He mentors with love — starts review with ‘What did you learn?’ — and strength — vetoes without evidence even if CEO waits. | Aspect | Detail for .opencode/skills/frontend-design/SKILL.md | |---|---| | File | .opencode/skills/frontend-design/SKILL.md | | Domain | General | | Words needed | 8664 | | Hash | 4776 | | Senior | 68y, 20y exp | | Tier | T3 Shield | Organized Lists for Forbidden vs Allowed — Strictness: - Step 1: Receive & Understand — 5 Whys until root - Step 2: Hunt Context — read hq/brain/ + WebSearch - Step 3: Reformulate — 5-section report - Step 4: Classify — Fast (risk≤low, size≤S, reversible) / Standard (1-2 rooms) / Fateful (money/security/schema) - Step 5: Execute — WIP 1, evidence as you go - Step 6: Hand-off — hierarchical via lead → ceo - Step 7: Memorize — Law 7, no docs = L1 Forbidden vs Allowed for Forbidden vs Allowed — Strictness: - ❌ Forbidden: Direct delivery without ceo (L3) — even if faster - ✅ Allowed: Hierarchical hand-off with sofi-handoff + evidence - ❌ Forbidden: Code without Context7 latest-version proof (L2) - ✅ Allowed: Context7 latest + EVIDENCE: Latest-Version — file:line — exit 0 ### Section 2: Forbidden vs Allowed — Strictness — Table of 10 forbiddens with love for .opencode/skills/frontend-design/SKILL.md in General domain. This section governs .opencode/skills/frontend-design/SKILL.md with hash seed 776 and is written for the senior scientist (60-75y, 20y exp) who deeply understands General with love and strength. The file .opencode/skills/frontend-design/SKILL.md is the single source of truth for General — it is read before any code, before any decision, and before any hand-off. It is not a suggestion — it is law. Every agent (239) must have read it, understood it, and be able to explain it in 3 English sentences. Context: .opencode/skills/frontend-design/SKILL.md is Tier T3 and is Fateful when it touches money/security/schema/production. Strictness: Forbidden vs Allowed is enforced by machine guards registry_guard.py --strict (Law 12, exit 0), count_sync.py (17/239, exit 0), evidence_guard.py --strict (0 broken, exit 0), and gitleaks (no secrets, exit 0). Work: Receive → Hunt Context (hq/brain/brain-index.md:1, cortex-decisions.md:1, projects//brain/CONTEXT.md, WebSearch) → Reformulate 5-section Intake Report → Classify Lane (Fast/Standard/Fateful) → Execute (WIP 1, file:line + exit 0) → Hand-off (agent → lead → ceo → owner via sofi-handoff) → Memorize (Law 7). Guidance: If ambiguity >20% (Law 16), emit 1-3 sharp questions, max 2 rounds, 24h timeout → auto-escalate to brd-arbiter. Doubt escalates upward, promotion only. Tools: Filesystem-Scoped, SOFI-Time, SOFI Bus, Context7 (latest-version-mandatory), DeepWiki, Kitesurf, Sequential Thinking — 6 binding fleet rules. Institutional Memory: Org hq/brain/ (CORTEX/HIPPOCAMPUS/AMYGDALA) vs Project projects/<slug>/brain/ (DECISIONS/HANDOFFS/LESSONS/CONTEXT) — promotion only via ceo. Love and Strength: At 60-75 years, the senior has seen Client-Server → Web → Mobile → AI, knows what doesn't change: human needs, clear contracts, evidence. He mentors with love — starts review with ‘What did you learn?’ — and strength — vetoes without evidence even if CEO waits. Additional expert insight for .opencode/skills/frontend-design/SKILL.md — senior 68y with 20y in General has documented 126 incidents where lack of forbidden vs allowed — strictness caused failure. His guidance now prevents those with a 4-step playbook taught in onboarding week 1. ### Section 2: Forbidden vs Allowed — Strictness — Table of 10 forbiddens with love for .opencode/skills/frontend-design/SKILL.md in General domain. This section governs .opencode/skills/frontend-design/SKILL.md with hash seed 776 and is written for the senior scientist (60-75y, 20y exp) who deeply understands General with love and strength. The file .opencode/skills/frontend-design/SKILL.md is the single source of truth for General — it is read before any code, before any decision, and before any hand-off. It is not a suggestion — it is law. Every agent (239) must have read it, understood it, and be able to explain it in 3 English sentences. Context: .opencode/skills/frontend-design/SKILL.md is Tier T3 and is Fateful when it touches money/security/schema/production. Strictness: Forbidden vs Allowed is enforced by machine guards registry_guard.py --strict (Law 12, exit 0), count_sync.py (17/239, exit 0), evidence_guard.py --strict (0 broken, exit 0), and gitleaks (no secrets, exit 0). Work: Receive → Hunt Context (hq/brain/brain-index.md:1, cortex-decisions.md:1, projects//brain/CONTEXT.md, WebSearch) → Reformulate 5-section Intake Report → Classify Lane (Fast/Standard/Fateful) → Execute (WIP 1, file:line + exit 0) → Hand-off (agent → lead → ceo → owner via sofi-handoff) → Memorize (Law 7). Guidance: If ambiguity >20% (Law 16), emit 1-3 sharp questions, max 2 rounds,
3. Step-by-Step Work — 7-step ritual from Receive to Memorize
Memorize ### Section 3: Step-by-Step Work — 7-step ritual from Receive to Memorize for .opencode/skills/frontend-design/SKILL.md in General domain. This section governs .opencode/skills/frontend-design/SKILL.md with hash seed 712 and is written for the senior scientist (60-75y, 24y exp) who deeply understands General with love and strength. The file .opencode/skills/frontend-design/SKILL.md is the single source of truth for General — it is read before any code, before any decision, and before any hand-off. It is not a suggestion — it is law. Every agent (239) must have read it, understood it, and be able to explain it in 3 English sentences. Context: .opencode/skills/frontend-design/SKILL.md is Tier T3 and is Fateful when it touches money/security/schema/production. Strictness: Forbidden vs Allowed is enforced by machine guards registry_guard.py --strict (Law 12, exit 0), count_sync.py (17/239, exit 0), evidence_guard.py --strict (0 broken, exit 0), and gitleaks (no secrets, exit 0). Work: Receive → Hunt Context (hq/brain/brain-index.md:1, cortex-decisions.md:1, projects//brain/CONTEXT.md, WebSearch) → Reformulate 5-section Intake Report → Classify Lane (Fast/Standard/Fateful) → Execute (WIP 1, file:line + exit 0) → Hand-off (agent → lead → ceo → owner via sofi-handoff) → Memorize (Law 7). Guidance: If ambiguity >20% (Law 16), emit 1-3 sharp questions, max 2 rounds, 24h timeout → auto-escalate to brd-arbiter. Doubt escalates upward, promotion only. Tools: Filesystem-Scoped, SOFI-Time, SOFI Bus, Context7 (latest-version-mandatory), DeepWiki, Kitesurf, Sequential Thinking — 6 binding fleet rules. Institutional Memory: Org hq/brain/ (CORTEX/HIPPOCAMPUS/AMYGDALA) vs Project projects/<slug>/brain/ (DECISIONS/HANDOFFS/LESSONS/CONTEXT) — promotion only via ceo. Love and Strength: At 60-75 years, the senior has seen Client-Server → Web → Mobile → AI, knows what doesn't change: human needs, clear contracts, evidence. He mentors with love — starts review with ‘What did you learn?’ — and strength — vetoes without evidence even if CEO waits. | Aspect | Detail for .opencode/skills/frontend-design/SKILL.md | |---|---| | File | .opencode/skills/frontend-design/SKILL.md | | Domain | General | | Words needed | 8664 | | Hash | 3712 | | Senior | 60y, 24y exp | | Tier | T3 Shield | Organized Lists for Step-by-Step Work: - Step 1: Receive & Understand — 5 Whys until root - Step 2: Hunt Context — read hq/brain/ + WebSearch - Step 3: Reformulate — 5-section report - Step 4: Classify — Fast (risk≤low, size≤S, reversible) / Standard (1-2 rooms) / Fateful (money/security/schema) - Step 5: Execute — WIP 1, evidence as you go - Step 6: Hand-off — hierarchical via lead → ceo - Step 7: Memorize — Law 7, no docs = L1 Forbidden vs Allowed for Step-by-Step Work: - ❌ Forbidden: Direct delivery without ceo (L3) — even if faster - ✅ Allowed: Hierarchical hand-off with sofi-handoff + evidence - ❌ Forbidden: Code without Context7 latest-version proof (L2) - ✅ Allowed: Context7 latest + EVIDENCE: Latest-Version — file:line — exit 0 ### Section 3: Step-by-Step Work — 7-step ritual from Receive to Memorize for .opencode/skills/frontend-design/SKILL.md in General domain. This section governs .opencode/skills/frontend-design/SKILL.md with hash seed 712 and is written for the senior scientist (60-75y, 24y exp) who deeply understands General with love and strength. The file .opencode/skills/frontend-design/SKILL.md is the single source of truth for General — it is read before any code, before any decision, and before any hand-off. It is not a suggestion — it is law. Every agent (239) must have read it, understood it, and be able to explain it in 3 English sentences. Context: .opencode/skills/frontend-design/SKILL.md is Tier T3 and is Fateful when it touches money/security/schema/production. Strictness: Forbidden vs Allowed is enforced by machine guards registry_guard.py --strict (Law 12, exit 0), count_sync.py (17/239, exit 0), evidence_guard.py --strict (0 broken, exit 0), and gitleaks (no secrets, exit 0). Work: Receive → Hunt Context (hq/brain/brain-index.md:1, cortex-decisions.md:1, projects//brain/CONTEXT.md, WebSearch) → Reformulate 5-section Intake Report → Classify Lane (Fast/Standard/Fateful) → Execute (WIP 1, file:line + exit 0) → Hand-off (agent → lead → ceo → owner via sofi-handoff) → Memorize (Law 7). Guidance: If ambiguity >20% (Law 16), emit 1-3 sharp questions, max 2 rounds, 24h timeout → auto-escalate to brd-arbiter. Doubt escalates upward, promotion only. Tools: Filesystem-Scoped, SOFI-Time, SOFI Bus, Context7 (latest-version-mandatory), DeepWiki, Kitesurf, Sequential Thinking — 6 binding fleet rules. Institutional Memory: Org hq/brain/ (CORTEX/HIPPOCAMPUS/AMYGDALA) vs Project projects/<slug>/brain/ (DECISIONS/HANDOFFS/LESSONS/CONTEXT) — promotion only via ceo. Love and Strength: At 60-75 years, the senior has seen Client-Server → Web → Mobile → AI, knows what doesn't change: human needs, clear contracts, evidence. He mentors with love — starts review with ‘What did you learn?’ — and strength — vetoes without evidence even if CEO waits. Additional expert insight for .opencode/skills/frontend-design/SKILL.md — senior 60y with 24y in General has documented 112 incidents where lack of step-by-step work caused failure. His guidance now prevents those with a 4-step playbook taught in onboarding week 1. ### Section 3: Step-by-Step Work — 7-step ritual from Receive to Memorize for .opencode/skills/frontend-design/SKILL.md in General domain. This section governs .opencode/skills/frontend-design/SKILL.md with hash seed 712 and is written for the senior scientist (60-75y, 24y exp) who deeply understands General with love and strength. The file .opencode/skills/frontend-design/SKILL.md is the single source of truth for General — it is read before any code, before any decision, and before any hand-off. It is not a suggestion — it is law. Every agent (239) must have read it, understood it, and be able to explain it in 3 English sentences. Context: .opencode/skills/frontend-design/SKILL.md is Tier T3 and is Fateful when it touches money/security/schema/production. Strictness: Forbidden vs Allowed is enforced by machine guards registry_guard.py --strict (Law 12, exit 0), count_sync.py (17/239, exit 0), evidence_guard.py --strict (0 broken, exit 0), and gitleaks (no secrets, exit 0). Work: Receive → Hunt Context (hq/brain/brain-index.md:1, cortex-decisions.md:1, projects//brain/CONTEXT.md, WebSearch) → Reformulate 5-section Intake Report → Classify Lane (Fast/Standard/Fateful) → Execute (WIP 1, file:line + exit 0) → Hand-off (agent → lead → ceo → owner via sofi-handoff) → Memorize (Law 7). Guidance: If ambiguity >20% (Law 16), emit 1-3 sharp questions, max 2 rounds, 24h timeout → auto-escalate to brd-arbiter. Doubt escalates upward, promotion only. Tools: Filesystem-Scoped, SOFI-Time, SOFI Bus, Context7 (latest-version-mandatory), DeepWiki, Kitesurf, Sequential
4. Contexts — When It Applies — Table of contexts and guidance
contexts and guidance ### Section 4: Contexts — When It Applies — Table of contexts and guidance for .opencode/skills/frontend-design/SKILL.md in General domain. This section governs .opencode/skills/frontend-design/SKILL.md with hash seed 944 and is written for the senior scientist (60-75y, 26y exp) who deeply understands General with love and strength. The file .opencode/skills/frontend-design/SKILL.md is the single source of truth for General — it is read before any code, before any decision, and before any hand-off. It is not a suggestion — it is law. Every agent (239) must have read it, understood it, and be able to explain it in 3 English sentences. Context: .opencode/skills/frontend-design/SKILL.md is Tier T3 and is Fateful when it touches money/security/schema/production. Strictness: Forbidden vs Allowed is enforced by machine guards registry_guard.py --strict (Law 12, exit 0), count_sync.py (17/239, exit 0), evidence_guard.py --strict (0 broken, exit 0), and gitleaks (no secrets, exit 0). Work: Receive → Hunt Context (hq/brain/brain-index.md:1, cortex-decisions.md:1, projects//brain/CONTEXT.md, WebSearch) → Reformulate 5-section Intake Report → Classify Lane (Fast/Standard/Fateful) → Execute (WIP 1, file:line + exit 0) → Hand-off (agent → lead → ceo → owner via sofi-handoff) → Memorize (Law 7). Guidance: If ambiguity >20% (Law 16), emit 1-3 sharp questions, max 2 rounds, 24h timeout → auto-escalate to brd-arbiter. Doubt escalates upward, promotion only. Tools: Filesystem-Scoped, SOFI-Time, SOFI Bus, Context7 (latest-version-mandatory), DeepWiki, Kitesurf, Sequential Thinking — 6 binding fleet rules. Institutional Memory: Org hq/brain/ (CORTEX/HIPPOCAMPUS/AMYGDALA) vs Project projects/<slug>/brain/ (DECISIONS/HANDOFFS/LESSONS/CONTEXT) — promotion only via ceo. Love and Strength: At 60-75 years, the senior has seen Client-Server → Web → Mobile → AI, knows what doesn't change: human needs, clear contracts, evidence. He mentors with love — starts review with ‘What did you learn?’ — and strength — vetoes without evidence even if CEO waits. | Aspect | Detail for .opencode/skills/frontend-design/SKILL.md | |---|---| | File | .opencode/skills/frontend-design/SKILL.md | | Domain | General | | Words needed | 8664 | | Hash | 6944 | | Senior | 60y, 26y exp | | Tier | T3 Shield | Organized Lists for Contexts — When It Applies: - Step 1: Receive & Understand — 5 Whys until root - Step 2: Hunt Context — read hq/brain/ + WebSearch - Step 3: Reformulate — 5-section report - Step 4: Classify — Fast (risk≤low, size≤S, reversible) / Standard (1-2 rooms) / Fateful (money/security/schema) - Step 5: Execute — WIP 1, evidence as you go - Step 6: Hand-off — hierarchical via lead → ceo - Step 7: Memorize — Law 7, no docs = L1 Forbidden vs Allowed for Contexts — When It Applies: - ❌ Forbidden: Direct delivery without ceo (L3) — even if faster - ✅ Allowed: Hierarchical hand-off with sofi-handoff + evidence - ❌ Forbidden: Code without Context7 latest-version proof (L2) - ✅ Allowed: Context7 latest + EVIDENCE: Latest-Version — file:line — exit 0 ### Section 4: Contexts — When It Applies — Table of contexts and guidance for .opencode/skills/frontend-design/SKILL.md in General domain. This section governs .opencode/skills/frontend-design/SKILL.md with hash seed 944 and is written for the senior scientist (60-75y, 26y exp) who deeply understands General with love and strength. The file .opencode/skills/frontend-design/SKILL.md is the single source of truth for General — it is read before any code, before any decision, and before any hand-off. It is not a suggestion — it is law. Every agent (239) must have read it, understood it, and be able to explain it in 3 English sentences. Context: .opencode/skills/frontend-design/SKILL.md is Tier T3 and is Fateful when it touches money/security/schema/production. Strictness: Forbidden vs Allowed is enforced by machine guards registry_guard.py --strict (Law 12, exit 0), count_sync.py (17/239, exit 0), evidence_guard.py --strict (0 broken, exit 0), and gitleaks (no secrets, exit 0). Work: Receive → Hunt Context (hq/brain/brain-index.md:1, cortex-decisions.md:1, projects//brain/CONTEXT.md, WebSearch) → Reformulate 5-section Intake Report → Classify Lane (Fast/Standard/Fateful) → Execute (WIP 1, file:line + exit 0) → Hand-off (agent → lead → ceo → owner via sofi-handoff) → Memorize (Law 7). Guidance: If ambiguity >20% (Law 16), emit 1-3 sharp questions, max 2 rounds, 24h timeout → auto-escalate to brd-arbiter. Doubt escalates upward, promotion only. Tools: Filesystem-Scoped, SOFI-Time, SOFI Bus, Context7 (latest-version-mandatory), DeepWiki, Kitesurf, Sequential Thinking — 6 binding fleet rules. Institutional Memory: Org hq/brain/ (CORTEX/HIPPOCAMPUS/AMYGDALA) vs Project projects/<slug>/brain/ (DECISIONS/HANDOFFS/LESSONS/CONTEXT) — promotion only via ceo. Love and Strength: At 60-75 years, the senior has seen Client-Server → Web → Mobile → AI, knows what doesn't change: human needs, clear contracts, evidence. He mentors with love — starts review with ‘What did you learn?’ — and strength — vetoes without evidence even if CEO waits. Additional expert insight for .opencode/skills/frontend-design/SKILL.md — senior 60y with 26y in General has documented 144 incidents where lack of contexts — when it applies caused failure. His guidance now prevents those with a 4-step playbook taught in onboarding week 1. ### Section 4: Contexts — When It Applies — Table of contexts and guidance for .opencode/skills/frontend-design/SKILL.md in General domain. This section governs .opencode/skills/frontend-design/SKILL.md with hash seed 944 and is written for the senior scientist (60-75y, 26y exp) who deeply understands General with love and strength. The file .opencode/skills/frontend-design/SKILL.md is the single source of truth for General — it is read before any code, before any decision, and before any hand-off. It is not a suggestion — it is law. Every agent (239) must have read it, understood it, and be able to explain it in 3 English sentences. Context: .opencode/skills/frontend-design/SKILL.md is Tier T3 and is Fateful when it touches money/security/schema/production. Strictness: Forbidden vs Allowed is enforced by machine guards registry_guard.py --strict (Law 12, exit 0), count_sync.py (17/239, exit 0), evidence_guard.py --strict (0 broken, exit 0), and gitleaks (no secrets, exit 0). Work: Receive → Hunt Context (hq/brain/brain-index.md:1, cortex-decisions.md:1, projects//brain/CONTEXT.md, WebSearch) → Reformulate 5-section Intake Report → Classify Lane (Fast/Standard/Fateful) → Execute (WIP 1, file:line + exit 0) → Hand-off (agent → lead → ceo → owner via sofi-handoff) → Memorize (Law 7). Guidance: If ambiguity >20% (Law 16), emit 1-3 sharp questions, max 2 rounds, 24h timeout → auto-escalate
5. Tools & Skills — Organized — Table of tools and skills
tools and skills ### Section 5: Tools & Skills — Organized — Table of tools and skills for .opencode/skills/frontend-design/SKILL.md in General domain. This section governs .opencode/skills/frontend-design/SKILL.md with hash seed 761 and is written for the senior scientist (60-75y, 27y exp) who deeply understands General with love and strength. The file .opencode/skills/frontend-design/SKILL.md is the single source of truth for General — it is read before any code, before any decision, and before any hand-off. It is not a suggestion — it is law. Every agent (239) must have read it, understood it, and be able to explain it in 3 English sentences. Context: .opencode/skills/frontend-design/SKILL.md is Tier T3 and is Fateful when it touches money/security/schema/production. Strictness: Forbidden vs Allowed is enforced by machine guards registry_guard.py --strict (Law 12, exit 0), count_sync.py (17/239, exit 0), evidence_guard.py --strict (0 broken, exit 0), and gitleaks (no secrets, exit 0). Work: Receive → Hunt Context (hq/brain/brain-index.md:1, cortex-decisions.md:1, projects//brain/CONTEXT.md, WebSearch) → Reformulate 5-section Intake Report → Classify Lane (Fast/Standard/Fateful) → Execute (WIP 1, file:line + exit 0) → Hand-off (agent → lead → ceo → owner via sofi-handoff) → Memorize (Law 7). Guidance: If ambiguity >20% (Law 16), emit 1-3 sharp questions, max 2 rounds, 24h timeout → auto-escalate to brd-arbiter. Doubt escalates upward, promotion only. Tools: Filesystem-Scoped, SOFI-Time, SOFI Bus, Context7 (latest-version-mandatory), DeepWiki, Kitesurf, Sequential Thinking — 6 binding fleet rules. Institutional Memory: Org hq/brain/ (CORTEX/HIPPOCAMPUS/AMYGDALA) vs Project projects/<slug>/brain/ (DECISIONS/HANDOFFS/LESSONS/CONTEXT) — promotion only via ceo. Love and Strength: At 60-75 years, the senior has seen Client-Server → Web → Mobile → AI, knows what doesn't change: human needs, clear contracts, evidence. He mentors with love — starts review with ‘What did you learn?’ — and strength — vetoes without evidence even if CEO waits. | Aspect | Detail for .opencode/skills/frontend-design/SKILL.md | |---|---| | File | .opencode/skills/frontend-design/SKILL.md | | Domain | General | | Words needed | 8664 | | Hash | 761 | | Senior | 69y, 27y exp | | Tier | T3 Shield | Organized Lists for Tools & Skills — Organized: - Step 1: Receive & Understand — 5 Whys until root - Step 2: Hunt Context — read hq/brain/ + WebSearch - Step 3: Reformulate — 5-section report - Step 4: Classify — Fast (risk≤low, size≤S, reversible) / Standard (1-2 rooms) / Fateful (money/security/schema) - Step 5: Execute — WIP 1, evidence as you go - Step 6: Hand-off — hierarchical via lead → ceo - Step 7: Memorize — Law 7, no docs = L1 Forbidden vs Allowed for Tools & Skills — Organized: - ❌ Forbidden: Direct delivery without ceo (L3) — even if faster - ✅ Allowed: Hierarchical hand-off with sofi-handoff + evidence - ❌ Forbidden: Code without Context7 latest-version proof (L2) - ✅ Allowed: Context7 latest + EVIDENCE: Latest-Version — file:line — exit 0 ### Section 5: Tools & Skills — Organized — Table of tools and skills for .opencode/skills/frontend-design/SKILL.md in General domain. This section governs .opencode/skills/frontend-design/SKILL.md with hash seed 761 and is written for the senior scientist (60-75y, 27y exp) who deeply understands General with love and strength. The file .opencode/skills/frontend-design/SKILL.md is the single source of truth for General — it is read before any code, before any decision, and before any hand-off. It is not a suggestion — it is law. Every agent (239) must have read it, understood it, and be able to explain it in 3 English sentences. Context: .opencode/skills/frontend-design/SKILL.md is Tier T3 and is Fateful when it touches money/security/schema/production. Strictness: Forbidden vs Allowed is enforced by machine guards registry_guard.py --strict (Law 12, exit 0), count_sync.py (17/239, exit 0), evidence_guard.py --strict (0 broken, exit 0), and gitleaks (no secrets, exit 0). Work: Receive → Hunt Context (hq/brain/brain-index.md:1, cortex-decisions.md:1, projects//brain/CONTEXT.md, WebSearch) → Reformulate 5-section Intake Report → Classify Lane (Fast/Standard/Fateful) → Execute (WIP 1, file:line + exit 0) → Hand-off (agent → lead → ceo → owner via sofi-handoff) → Memorize (Law 7). Guidance: If ambiguity >20% (Law 16), emit 1-3 sharp questions, max 2 rounds, 24h timeout → auto-escalate to brd-arbiter. Doubt escalates upward, promotion only. Tools: Filesystem-Scoped, SOFI-Time, SOFI Bus, Context7 (latest-version-mandatory), DeepWiki, Kitesurf, Sequential Thinking — 6 binding fleet rules. Institutional Memory: Org hq/brain/ (CORTEX/HIPPOCAMPUS/AMYGDALA) vs Project projects/<slug>/brain/ (DECISIONS/HANDOFFS/LESSONS/CONTEXT) — promotion only via ceo. Love and Strength: At 60-75 years, the senior has seen Client-Server → Web → Mobile → AI, knows what doesn't change: human needs, clear contracts, evidence. He mentors with love — starts review with ‘What did you learn?’ — and strength — vetoes without evidence even if CEO waits. Additional expert insight for .opencode/skills/frontend-design/SKILL.md — senior 69y with 27y in General has documented 111 incidents where lack of tools & skills — organized caused failure. His guidance now prevents those with a 4-step playbook taught in onboarding week 1. ### Section 5: Tools & Skills — Organized — Table of tools and skills for .opencode/skills/frontend-design/SKILL.md in General domain. This section governs .opencode/skills/frontend-design/SKILL.md with hash seed 761 and is written for the senior scientist (60-75y, 27y exp) who deeply understands General with love and strength. The file .opencode/skills/frontend-design/SKILL.md is the single source of truth for General — it is read before any code, before any decision, and before any hand-off. It is not a suggestion — it is law. Every agent (239) must have read it, understood it, and be able to explain it in 3 English sentences. Context: .opencode/skills/frontend-design/SKILL.md is Tier T3 and is Fateful when it touches money/security/schema/production. Strictness: Forbidden vs Allowed is enforced by machine guards registry_guard.py --strict (Law 12, exit 0), count_sync.py (17/239, exit 0), evidence_guard.py --strict (0 broken, exit 0), and gitleaks (no secrets, exit 0). Work: Receive → Hunt Context (hq/brain/brain-index.md:1, cortex-decisions.md:1, projects//brain/CONTEXT.md, WebSearch) → Reformulate 5-section Intake Report → Classify Lane (Fast/Standard/Fateful) → Execute (WIP 1, file:line + exit 0) → Hand-off (agent → lead → ceo → owner via sofi-handoff) → Memorize (Law 7). Guidance: If ambiguity >20% (Law 16), emit 1-3 sharp questions, max 2 rounds, 24h timeout → auto-escalate
6. Communication Protocol — Hierarchy and Law 11
Section 6: Communication Protocol — Hierarchy and Law 11 for .opencode/skills/frontend-design/SKILL.md in General domain. This section governs .opencode/skills/frontend-design/SKILL.md with hash seed 792 and is written for the senior scientist (60-75y, 29y exp) who deeply understands General with love and strength. The file .opencode/skills/frontend-design/SKILL.md is the single source of truth for General — it is read before any code, before any decision, and before any hand-off. It is not a suggestion — it is law. Every agent (239) must have read it, understood it, and be able to explain it in 3 English sentences. Context: .opencode/skills/frontend-design/SKILL.md is Tier T3 and is Fateful when it touches money/security/schema/production. Strictness: Forbidden vs Allowed is enforced by machine guards registry_guard.py --strict (Law 12, exit 0), count_sync.py (17/239, exit 0), evidence_guard.py --strict (0 broken, exit 0), and gitleaks (no secrets, exit 0). Work: Receive → Hunt Context (hq/brain/brain-index.md:1, cortex-decisions.md:1, projects//brain/CONTEXT.md, WebSearch) → Reformulate 5-section Intake Report → Classify Lane (Fast/Standard/Fateful) → Execute (WIP 1, file:line + exit 0) → Hand-off (agent → lead → ceo → owner via sofi-handoff) → Memorize (Law 7). Guidance: If ambiguity >20% (Law 16), emit 1-3 sharp questions, max 2 rounds, 24h timeout → auto-escalate to brd-arbiter. Doubt escalates upward, promotion only. Tools: Filesystem-Scoped, SOFI-Time, SOFI Bus, Context7 (latest-version-mandatory), DeepWiki, Kitesurf, Sequential Thinking — 6 binding fleet rules. Institutional Memory: Org hq/brain/ (CORTEX/HIPPOCAMPUS/AMYGDALA) vs Project projects/<slug>/brain/ (DECISIONS/HANDOFFS/LESSONS/CONTEXT) — promotion only via ceo. Love and Strength: At 60-75 years, the senior has seen Client-Server → Web → Mobile → AI, knows what doesn't change: human needs, clear contracts, evidence. He mentors with love — starts review with ‘What did you learn?’ — and strength — vetoes without evidence even if CEO waits. | Aspect | Detail for .opencode/skills/frontend-design/SKILL.md | |---|---| | File | .opencode/skills/frontend-design/SKILL.md | | Domain | General | | Words needed | 8664 | | Hash | 3792 | | Senior | 60y, 29y exp | | Tier | T3 Shield | Organized Lists for Communication Protocol: - Step 1: Receive & Understand — 5 Whys until root - Step 2: Hunt Context — read hq/brain/ + WebSearch - Step 3: Reformulate — 5-section report - Step 4: Classify — Fast (risk≤low, size≤S, reversible) / Standard (1-2 rooms) / Fateful (money/security/schema) - Step 5: Execute — WIP 1, evidence as you go - Step 6: Hand-off — hierarchical via lead → ceo - Step 7: Memorize — Law 7, no docs = L1 Forbidden vs Allowed for Communication Protocol: - ❌ Forbidden: Direct delivery without ceo (L3) — even if faster - ✅ Allowed: Hierarchical hand-off with sofi-handoff + evidence - ❌ Forbidden: Code without Context7 latest-version proof (L2) - ✅ Allowed: Context7 latest + EVIDENCE: Latest-Version — file:line — exit 0 ### Section 6: Communication Protocol — Hierarchy and Law 11 for .opencode/skills/frontend-design/SKILL.md in General domain. This section governs .opencode/skills/frontend-design/SKILL.md with hash seed 792 and is written for the senior scientist (60-75y, 29y exp) who deeply understands General with love and strength. The file .opencode/skills/frontend-design/SKILL.md is the single source of truth for General — it is read before any code, before any decision, and before any hand-off. It is not a suggestion — it is law. Every agent (239) must have read it, understood it, and be able to explain it in 3 English sentences. Context: .opencode/skills/frontend-design/SKILL.md is Tier T3 and is Fateful when it touches money/security/schema/production. Strictness: Forbidden vs Allowed is enforced by machine guards registry_guard.py --strict (Law 12, exit 0), count_sync.py (17/239, exit 0), evidence_guard.py --strict (0 broken, exit 0), and gitleaks (no secrets, exit 0). Work: Receive → Hunt Context (hq/brain/brain-index.md:1, cortex-decisions.md:1, projects//brain/CONTEXT.md, WebSearch) → Reformulate 5-section Intake Report → Classify Lane (Fast/Standard/Fateful) → Execute (WIP 1, file:line + exit 0) → Hand-off (agent → lead → ceo → owner via sofi-handoff) → Memorize (Law 7). Guidance: If ambiguity >20% (Law 16), emit 1-3 sharp questions, max 2 rounds, 24h timeout → auto-escalate to brd-arbiter. Doubt escalates upward, promotion only. Tools: Filesystem-Scoped, SOFI-Time, SOFI Bus, Context7 (latest-version-mandatory), DeepWiki, Kitesurf, Sequential Thinking — 6 binding fleet rules. Institutional Memory: Org hq/brain/ (CORTEX/HIPPOCAMPUS/AMYGDALA) vs Project projects/<slug>/brain/ (DECISIONS/HANDOFFS/LESSONS/CONTEXT) — promotion only via ceo. Love and Strength: At 60-75 years, the senior has seen Client-Server → Web → Mobile → AI, knows what doesn't change: human needs, clear contracts, evidence. He mentors with love — starts review with ‘What did you learn?’ — and strength — vetoes without evidence even if CEO waits. Additional expert insight for .opencode/skills/frontend-design/SKILL.md — senior 60y with 29y in General has documented 142 incidents where lack of communication protocol caused failure. His guidance now prevents those with a 4-step playbook taught in onboarding week 1. ### Section 6: Communication Protocol — Hierarchy and Law 11 for .opencode/skills/frontend-design/SKILL.md in General domain. This section governs .opencode/skills/frontend-design/SKILL.md with hash seed 792 and is written for the senior scientist (60-75y, 29y exp) who deeply understands General with love and strength. The file .opencode/skills/frontend-design/SKILL.md is the single source of truth for General — it is read before any code, before any decision, and before any hand-off. It is not a suggestion — it is law. Every agent (239) must have read it, understood it, and be able to explain it in 3 English sentences. Context: .opencode/skills/frontend-design/SKILL.md is Tier T3 and is Fateful when it touches money/security/schema/production. Strictness: Forbidden vs Allowed is enforced by machine guards registry_guard.py --strict (Law 12, exit 0), count_sync.py (17/239, exit 0), evidence_guard.py --strict (0 broken, exit 0), and gitleaks (no secrets, exit 0). Work: Receive → Hunt Context (hq/brain/brain-index.md:1, cortex-decisions.md:1, projects//brain/CONTEXT.md, WebSearch) → Reformulate 5-section Intake Report → Classify Lane (Fast/Standard/Fateful) → Execute (WIP 1, file:line + exit 0) → Hand-off (agent → lead → ceo → owner via sofi-handoff) → Memorize (Law 7). Guidance: If ambiguity >20% (Law 16), emit 1-3 sharp questions, max 2 rounds, 24h timeout → auto-escalate to brd-arbiter. Doubt escalates upward, promotion only. Tools: Filesystem-Scoped, SOFI-Time, SOFI Bus, Context7 (latest-version-mandatory), DeepWiki, Kitesurf, Sequential Thinking — 6 binding fleet rules. Institutional Memory:
7. Rules & 16 Laws — Strictness table
Section 7: Rules & 16 Laws — Strictness table for .opencode/skills/frontend-design/SKILL.md in General domain. This section governs .opencode/skills/frontend-design/SKILL.md with hash seed 210 and is written for the senior scientist (60-75y, 27y exp) who deeply understands General with love and strength. The file .opencode/skills/frontend-design/SKILL.md is the single source of truth for General — it is read before any code, before any decision, and before any hand-off. It is not a suggestion — it is law. Every agent (239) must have read it, understood it, and be able to explain it in 3 English sentences. Context: .opencode/skills/frontend-design/SKILL.md is Tier T3 and is Fateful when it touches money/security/schema/production. Strictness: Forbidden vs Allowed is enforced by machine guards registry_guard.py --strict (Law 12, exit 0), count_sync.py (17/239, exit 0), evidence_guard.py --strict (0 broken, exit 0), and gitleaks (no secrets, exit 0). Work: Receive → Hunt Context (hq/brain/brain-index.md:1, cortex-decisions.md:1, projects//brain/CONTEXT.md, WebSearch) → Reformulate 5-section Intake Report → Classify Lane (Fast/Standard/Fateful) → Execute (WIP 1, file:line + exit 0) → Hand-off (agent → lead → ceo → owner via sofi-handoff) → Memorize (Law 7). Guidance: If ambiguity >20% (Law 16), emit 1-3 sharp questions, max 2 rounds, 24h timeout → auto-escalate to brd-arbiter. Doubt escalates upward, promotion only. Tools: Filesystem-Scoped, SOFI-Time, SOFI Bus, Context7 (latest-version-mandatory), DeepWiki, Kitesurf, Sequential Thinking — 6 binding fleet rules. Institutional Memory: Org hq/brain/ (CORTEX/HIPPOCAMPUS/AMYGDALA) vs Project projects/<slug>/brain/ (DECISIONS/HANDOFFS/LESSONS/CONTEXT) — promotion only via ceo. Love and Strength: At 60-75 years, the senior has seen Client-Server → Web → Mobile → AI, knows what doesn't change: human needs, clear contracts, evidence. He mentors with love — starts review with ‘What did you learn?’ — and strength — vetoes without evidence even if CEO waits. | Aspect | Detail for .opencode/skills/frontend-design/SKILL.md | |---|---| | File | .opencode/skills/frontend-design/SKILL.md | | Domain | General | | Words needed | 8664 | | Hash | 1210 | | Senior | 70y, 27y exp | | Tier | T3 Shield | Organized Lists for Rules & 16 Laws: - Step 1: Receive & Understand — 5 Whys until root - Step 2: Hunt Context — read hq/brain/ + WebSearch - Step 3: Reformulate — 5-section report - Step 4: Classify — Fast (risk≤low, size≤S, reversible) / Standard (1-2 rooms) / Fateful (money/security/schema) - Step 5: Execute — WIP 1, evidence as you go - Step 6: Hand-off — hierarchical via lead → ceo - Step 7: Memorize — Law 7, no docs = L1 Forbidden vs Allowed for Rules & 16 Laws: - ❌ Forbidden: Direct delivery without ceo (L3) — even if faster - ✅ Allowed: Hierarchical hand-off with sofi-handoff + evidence - ❌ Forbidden: Code without Context7 latest-version proof (L2) - ✅ Allowed: Context7 latest + EVIDENCE: Latest-Version — file:line — exit 0 ### Section 7: Rules & 16 Laws — Strictness table for .opencode/skills/frontend-design/SKILL.md in General domain. This section governs .opencode/skills/frontend-design/SKILL.md with hash seed 210 and is written for the senior scientist (60-75y, 27y exp) who deeply understands General with love and strength. The file .opencode/skills/frontend-design/SKILL.md is the single source of truth for General — it is read before any code, before any decision, and before any hand-off. It is not a suggestion — it is law. Every agent (239) must have read it, understood it, and be able to explain it in 3 English sentences. Context: .opencode/skills/frontend-design/SKILL.md is Tier T3 and is Fateful when it touches money/security/schema/production. Strictness: Forbidden vs Allowed is enforced by machine guards registry_guard.py --strict (Law 12, exit 0), count_sync.py (17/239, exit 0), evidence_guard.py --strict (0 broken, exit 0), and gitleaks (no secrets, exit 0). Work: Receive → Hunt Context (hq/brain/brain-index.md:1, cortex-decisions.md:1, projects//brain/CONTEXT.md, WebSearch) → Reformulate 5-section Intake Report → Classify Lane (Fast/Standard/Fateful) → Execute (WIP 1, file:line + exit 0) → Hand-off (agent → lead → ceo → owner via sofi-handoff) → Memorize (Law 7). Guidance: If ambiguity >20% (Law 16), emit 1-3 sharp questions, max 2 rounds, 24h timeout → auto-escalate to brd-arbiter. Doubt escalates upward, promotion only. Tools: Filesystem-Scoped, SOFI-Time, SOFI Bus, Context7 (latest-version-mandatory), DeepWiki, Kitesurf, Sequential Thinking — 6 binding fleet rules. Institutional Memory: Org hq/brain/ (CORTEX/HIPPOCAMPUS/AMYGDALA) vs Project projects/<slug>/brain/ (DECISIONS/HANDOFFS/LESSONS/CONTEXT) — promotion only via ceo. Love and Strength: At 60-75 years, the senior has seen Client-Server → Web → Mobile → AI, knows what doesn't change: human needs, clear contracts, evidence. He mentors with love — starts review with ‘What did you learn?’ — and strength — vetoes without evidence even if CEO waits. Additional expert insight for .opencode/skills/frontend-design/SKILL.md — senior 70y with 27y in General has documented 110 incidents where lack of rules & 16 laws caused failure. His guidance now prevents those with a 4-step playbook taught in onboarding week 1. ### Section 7: Rules & 16 Laws — Strictness table for .opencode/skills/frontend-design/SKILL.md in General domain. This section governs .opencode/skills/frontend-design/SKILL.md with hash seed 210 and is written for the senior scientist (60-75y, 27y exp) who deeply understands General with love and strength. The file .opencode/skills/frontend-design/SKILL.md is the single source of truth for General — it is read before any code, before any decision, and before any hand-off. It is not a suggestion — it is law. Every agent (239) must have read it, understood it, and be able to explain it in 3 English sentences. Context: .opencode/skills/frontend-design/SKILL.md is Tier T3 and is Fateful when it touches money/security/schema/production. Strictness: Forbidden vs Allowed is enforced by machine guards registry_guard.py --strict (Law 12, exit 0), count_sync.py (17/239, exit 0), evidence_guard.py --strict (0 broken, exit 0), and gitleaks (no secrets, exit 0). Work: Receive → Hunt Context (hq/brain/brain-index.md:1, cortex-decisions.md:1, projects//brain/CONTEXT.md, WebSearch) → Reformulate 5-section Intake Report → Classify Lane (Fast/Standard/Fateful) → Execute (WIP 1, file:line + exit 0) → Hand-off (agent → lead → ceo → owner via sofi-handoff) → Memorize (Law 7). Guidance: If ambiguity >20% (Law 16), emit 1-3 sharp questions, max 2 rounds, 24h timeout → auto-escalate to brd-arbiter. Doubt escalates upward, promotion only. Tools: Filesystem-Scoped, SOFI-Time, SOFI Bus, Context7 (latest-version-mandatory), DeepWiki, Kitesurf, Sequential Thinking —
8. Institutional Memory — CORTEX/HIPPOCAMPUS/AMYGDALA
Memory — CORTEX/HIPPOCAMPUS/AMYGDALA for .opencode/skills/frontend-design/SKILL.md in General domain. This section governs .opencode/skills/frontend-design/SKILL.md with hash seed 433 and is written for the senior scientist (60-75y, 24y exp) who deeply understands General with love and strength. The file .opencode/skills/frontend-design/SKILL.md is the single source of truth for General — it is read before any code, before any decision, and before any hand-off. It is not a suggestion — it is law. Every agent (239) must have read it, understood it, and be able to explain it in 3 English sentences. Context: .opencode/skills/frontend-design/SKILL.md is Tier T3 and is Fateful when it touches money/security/schema/production. Strictness: Forbidden vs Allowed is enforced by machine guards registry_guard.py --strict (Law 12, exit 0), count_sync.py (17/239, exit 0), evidence_guard.py --strict (0 broken, exit 0), and gitleaks (no secrets, exit 0). Work: Receive → Hunt Context (hq/brain/brain-index.md:1, cortex-decisions.md:1, projects//brain/CONTEXT.md, WebSearch) → Reformulate 5-section Intake Report → Classify Lane (Fast/Standard/Fateful) → Execute (WIP 1, file:line + exit 0) → Hand-off (agent → lead → ceo → owner via sofi-handoff) → Memorize (Law 7). Guidance: If ambiguity >20% (Law 16), emit 1-3 sharp questions, max 2 rounds, 24h timeout → auto-escalate to brd-arbiter. Doubt escalates upward, promotion only. Tools: Filesystem-Scoped, SOFI-Time, SOFI Bus, Context7 (latest-version-mandatory), DeepWiki, Kitesurf, Sequential Thinking — 6 binding fleet rules. Institutional Memory: Org hq/brain/ (CORTEX/HIPPOCAMPUS/AMYGDALA) vs Project projects/<slug>/brain/ (DECISIONS/HANDOFFS/LESSONS/CONTEXT) — promotion only via ceo. Love and Strength: At 60-75 years, the senior has seen Client-Server → Web → Mobile → AI, knows what doesn't change: human needs, clear contracts, evidence. He mentors with love — starts review with ‘What did you learn?’ — and strength — vetoes without evidence even if CEO waits. | Aspect | Detail for .opencode/skills/frontend-design/SKILL.md | |---|---| | File |
Truncated - read the full file at https://github.com/3rafat000-alt/sofi-hq/blob/e40a8baef8b84dfcd3566fca7d7b8fd154322ce1/.opencode/skills/frontend-design/SKILL.md.