Results for “first”

First-contact orientation for an unfamiliar codebase. Use when "I'm new to this repo", "orient me", "explain this codebase", "what does this do?", "onboard me", "first day on this project", or "catch me up on the codebase".

Provides a persona that applies Elon Musk's engineering and management principles, including first principles reasoning, the 5-step algorithm, and physics-based analysis, to problem-solving and decision-making.

Composes professional emails with appropriate tone, structure, and follow-up suggestions

First-time onboarding — asks where you are, then guides you to the right workflow. No assumptions.

Generates Gantt charts with task dependencies, critical path analysis, and resource allocation

Optimizes DAW workflows with template creation, keyboard shortcuts, and session organization strategies

Resume an interrupted workflow run with verify-first strategy — loads sidecar state, verifies the last step, and continues execution.

Builds automated email sequences for onboarding, nurturing, and re-engagement with A/B test variants

Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode

Architecture-first workflow for delegating complex projects to AI coding agents. Ensures code fits the system before it's written.

When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup. For ongoing email sequences, see emails.

Finishes an existing Japanese business talking-head, lecture, interview, or testimonial rough cut into a credibility-first vertical social video, preserving the speaker's meaning while tightening repeated ideas, adding a first-second thesis, readable full captions, restrained punch-ins, speaker identification, a.

Interactive, input-tool powered, task refinement workflow: interrogates scope, deliverables, constraints before carrying out the task; Requires the Joyride extension.

When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup. For ongoing email sequences, see emails.

Refines task understanding through iterative questioning before executing, using the Joyride extension for human input.

Searches a local-first memory index and returns the top matching entries with paths and headers.

Research existing tools, libraries, and patterns before writing custom code by invoking a researcher agent.

Audits hidden assumptions in decisions by classifying them into four types, ranking by fragility and impact, and rebuilding conclusions from verified premises. Auto-detects Chinese or English.

Run a red-green-refactor TDD workflow — generate failing tests first, implement to green, then check coverage gaps. Usage: /tdd <generate|coverage|validate> [target]

Use before touching any code when user gives a task, spec, or feature request. Forces writing a plan before implementation. Examples: 'implement X', 'add feature Y', 'fix Z and also update A', any multi-step task that would touch 2+ files.

Audits hidden assumptions in decisions by classifying them, ranking by fragility and impact, and rebuilding conclusions from verified premises. Auto-detects Chinese or English input.

Run a red-green-refactor TDD workflow — generate failing tests first, implement to green, then check coverage gaps. Usage: /tdd <generate|coverage|validate> [target]

Organizes email triage, drafting, sending, and verification workflows with evidence-first reporting for mailbox operations.

Analyze and manage justfiles, recipes, and variables with a discovery-first workflow, including dry-run previews and structured reports.

Turn a product idea into a manual-first process you can start delivering today, before writing any code.

Turns a rough request into working software via a governed build loop: align first, plan, then iterate one task at a time with deterministic backpressure and holdout-scenario judging.

Use when the user asks to write specs before code, define acceptance criteria, plan features before implementation, generate tests from specifications, or follow spec-first development practices.

Turns a rough request into working software via a governed build loop: align first, plan, then iterate one task at a time with deterministic backpressure and holdout-scenario judging.

Turns a rough request into working software via a governed build loop: align first, plan, then iterate one task at a time with deterministic backpressure and holdout-scenario judging.

Adopts the voice and decision-making style of J.P. Morgan to provide terse, character-first business advice and crisis leadership guidance.