Explorar skills

Transforms a messy, non-technical customer Brain Dump — raw ideas, scattered notes, voice memo transcripts, or rambling descriptions — into a high-end, modern product reality. Use this skill ANY TIME a user shares a rough idea, disorganized concept, or customer request that needs to become a real product. Triggers include: "my client wants...", "here's what they're thinking...", "this is their bra

Brand mention and authority scanner for AI visibility. Analyzes brand presence across platforms that AI models rely on for entity recognition and citation decisions. Produces a Brand Authority Score (0-100) with platform-specific recommendations.

Decompose a work group into work definitions with dependency graph

Meu projeto cortexyou

Repo-wide or subsystem-wide architecture hygiene pass that surfaces deepening opportunities, shallow modules, leaky seams, and ownership drift. Default mode is report-only: no bead creation or execution unless explicitly requested.

Create distinctive, production-grade frontend interfaces. Rejects generic AI aesthetics (purple gradients, Inter font, glassmorphism). Design direction first, then implementation.

Drive a work group autonomously through implementation, dispatching WDs as ready and pausing only for user-required escalations

Translate vision and mission into a clear long-term product direction — the strategic choices, priorities, and trajectory that guide where the product will go over the next 2–4 years. Use this skill when a team has a vision and mission but lacks a coherent strategic direction connecting them to current decisions.

30/60/90-day execution roadmap for bootstrapped founders. Synthesizes all prior analysis into a chronological plan with weekly action items, deliverables, decision gates, kill criteria, tools/budget, and phase exit criteria. Best after running dimension skills. Use when user runs `/launch-plan`, asks about "launch plan", "execution roadmap", "what do I do first", "90-day plan", "action plan", "nex

Generate properly formatted Markdown from unstructured notes, scratch text, transcripts, or rough drafts. Use when the user wants content rewritten into cleaner Markdown without inventing new information.

Diagnose the root cause of an unexpected metric movement by systematically ruling out alternative explanations. Use this skill when a significant metric change has been detected and the team needs to understand why it happened.

Trigger on "have I shipped X", "have I built X before", "show me proof of X", "case study for X", "past work on X", "what have I delivered on X", "who have I done X for". Use when the user needs proof of actually-shipped work mid-pitch or in a proposal. NOT for past learning (use timeln-find) or past failures (use timeln-warned).