chohra-med

Health-check the memory bank, rules, and index — flag stale, contradictory, or redundant entries and spec↔code drift. Use when Malik says 'audit the bank', 'is the memory stale', 'check spec harness health', or 'clean up the rules'.

Run the SDD pipeline over tasks.md: implement → test → VERIFY → review, one task at a time, under the ratchet. Use when Malik says 'build it', 'run the pipeline', 'implement the tasks', or 'ship this feature'. Each task gated by the separate verifier; lessons harvested by learn.

Bind the 6 SDD agents to THIS project's rules — fill each agent's GEN:rules region with its concern's real rules (implementer←Coding, tester←Testing+commands, reviewer←Reviewing, researcher/planner←Architecture, verifier←goal). Use when Malik says 'generate the agents', 'make the agents project-specific', 'bind agents to the rules', or right after rules are created/updated. If no rules exist yet, it routes to rules-generation (3 sources: structure + project best-practice + the internet) first. Idempotent; re-run after learn updates a rule.

Add or refresh Spec Harness in a repo — greenfield (new) or existing (integrate), idempotent. Use when Malik says 'install spec harness', 'set this repo up with spec harness', 'integrate spec harness into X', or 'start a new spec-harness project'. Runs the interview (mode, stack, constraints, work-intake source, learning goals, regression guards) and scaffolds the bank + agents + commands + skills without clobbering existing CLAUDE.md/AGENTS.md.

The learning loop — turn feedback, a correction, or a verifier-FAIL root cause into one enforced rule injected into the ratchet (AGENTS.md/ai_rules), dated. Use when Malik says 'learn this', 'remember not to do X', 'capture this lesson', 'don't do that again', or right after he corrects you. Closes the loop the verifier opens; emits an optional human lesson too.

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.

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 here', or when working in a monorepo with mixed stacks. Each section is owned by one SDD agent; deepest-wins cascade.

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 sub-skills and enforces the 3 pillars (memory bank · SDD · Harness).

Audit an app codebase for MCP + analytics + onboarding readiness AND MCP security posture, and produce an honest readiness scorecard as Markdown. Answers one question: is this app instrumented so an AI can actually SEE the funnel and help you act on it, without leaking data doing it? Use whenever someone asks "is my app ready for an MCP / for AI to help me improve onboarding", "audit my analytics", "readiness score", "can an agent reach my activation data", "is my MCP server safe / leaking", or points this skill at a repo and asks how instrumented it is. Works on any codebase (RN/Expo, web, backend); product-neutral checks.

Design and build a safe, useful MCP server that exposes your app's own data (analytics, funnel, revenue, crashes) to an AI assistant: read-only, least-privilege, AI-consumable. Use when someone asks "how do i build an MCP server for my app", "expose my analytics/funnel to my AI", "make my app's data reachable by Claude/Cursor", "wire an MCP over my backend", or "MCP security best practices". Enforces a security layer (read-only, field allowlist, no secrets in tool output, aggregate-not-row-level) and usability rules (Markdown output, few well-named tools) so the server helps without leaking.

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 and wants the output to match an existing brand instead of looking like generic AI UI. Triggers on "design this screen", "build a UI for", "make this on-brand", "redesign", "generate a page/component", "use /design", or any task that will produce visual interface.

Apply the Colorway C brand and design system when building any Code Meet AI or Malik Chohra surface (website, landing page, newsletter, component, social asset, README). Premium editorial, dark-first, one muted-teal accent, blinking teal cursor signature, hairline structure, Bricolage Grotesque + Geist + Geist Mono. Triggers on "colorway c", "code meet ai brand", "malik brand", "code meet ai design", or any request to make something on-brand for Code Meet AI / Malik Chohra.