Skill Claude CodeCodex
Turn a spec into a design.md (the 'how' — architecture decisions). Use when Malik says 'plan the implementation', 'how should we build this', or 'design this'. Second SDD step.
Skill Claude CodeCodex
Turn a spec into a design.md (the 'how' — architecture decisions). Use when Malik says 'plan the implementation', 'how should we build this', or 'design this'. Second SDD step.
Skill Claude CodeCodex
Per-directory rules — resolve the nearest RULES.md for a path (coding/architecture/packages/testing/reviewing), or generate it from a directory's real code when missing. Use when Malik says 'different directories have different rules', 'add rules per directory', 'each package needs its own rules', 'what rules apply…
Skill Claude CodeCodex
Turn a rough brief into a structured, testable spec.md (the 'what'). Use when Malik says 'spec this', 'write the spec for X', or 'what are the requirements'. First SDD step.
Skill Claude CodeCodex
Break a design into atomic, ordered, testable tasks.md. Use when Malik says 'break this into tasks', 'task it out', or 'what are the steps'. Third SDD step.
Skill Claude CodeCodex
Intake work into the SDD pipeline — pull tickets from a connected ticket MCP (Linear/GitHub/Jira) or define an inline plan. Use when Malik says 'pull my tickets', 'grab the Linear issues', 'turn this into specs', 'plan this work', or 'what should I build next'. Produces specs/NNN-/ ready for build.
Skill Claude CodeCodex
Run the verifier alone — a separate clean-context agent that returns PASS/FAIL against goal.md (not the agent that wrote the code). Use when Malik says 'verify it', 'is it actually done', 'check against the goal', or 'did this pass'. Tests passing ≠ goal met.
Skill Claude CodeCodex
The Spec Harness orchestrator — spec-driven development wrapped in a harness (ratchet + verifier + learning loop) over a persistent memory bank. Use when Malik says 'use spec harness', 'run the spec harness', 'spec-harness this feature', or wants the full spec→plan→tasks→build→verify→learn flow. Routes to the…
Cursor rule Cursor
Feature-first architecture is a design pattern that organizes code by business features rather than technical layers. This approach promotes better maintainability, scalability, and team collaboration by keeping related functionality together and reducing coupling between different parts of the application.
Cursor rule Cursor
This document outlines the essential rules and guidelines for developing with the MobileLauncher LT boilerplate. Follow these rules to maintain consistency, scalability, and code quality across the project.
Cursor rule Cursor
Advanced Best Practices covering Error Handling, Environment Variables, Performance, and Accessibility rules.
Instructions file CodexOpenCode
Instructions for chohra-med/expo_boilerplate, covering agents.md — mobilelauncher lt, project and 🎯 the master rules location.
Instructions file
Instructions for chohra-med/expo_boilerplate, covering claude.md — mobilelauncher lt, 🌿 branches — the trunk is development, there is no main, project skill, what this project is and the master rules.
chohra-med/claude_design_skill
Skill Claude CodeCodex
Take a UI from a one-line idea to on-brand, shippable design with Claude, in the correct order — brand foundation first, then components, screens, interactions, accessibility, and only then generation via /design. Use whenever someone wants to design, redesign, or generate a screen, page, component, or onboarding flow…