wip-quickstart

Scaffolds new code projects from rough briefs through structured intake and workspace setup.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/tommylower/cortex --skill wip-quickstart-tommylower
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wip-quickstart
Source: https://github.com/tommylower/cortex/tree/main/agent-workflows/wip-quickstart
Command: npx skills add https://github.com/tommylower/cortex --skill wip-quickstart-tommylower

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Starting a new project from a rough idea, voice dump, or ticket often means repeating context, making ad-hoc stack decisions, and manually wiring up workspace conventions. This Skill turns supplied context into a compact project brief and the smallest operable codebase without redundant questioning. ## Core Features & Use Cases - Context-first intake: Extracts known facts from voice notes, tickets, conversations, or existing directories before asking only material questions. - Action boundary control: Classifies requests as Brief, Propose, or Scaffold mode so local edits and external actions stay within explicit authorization. - Workspace and scaffold orchestration: Delegates workspace structure to the workspace-setup skill and applies web project defaults (Next.js, TypeScript, Tailwind, Supabase, Vercel, Bun) when appropriate. - Use Case: You paste a voice-note transcript describing a client web app idea. The Skill produces a project brief, sets up the workspace layer, scaffolds a Next.js project with the default stack, and verifies install and build commands pass. ## Quick Start Ask the agent to scaffold a new project from your attached brief or voice note using the wip-quickstart workflow.

Frequently Asked Questions about wip-quickstart

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a new project from a rough idea or voice note?▼

Provide the voice dump, ticket, or conversation as context. The workflow extracts known facts, asks only questions that change the scaffold or privacy boundary, forms a project brief, then creates the smallest operable project after you authorize scaffolding.

What is the difference between Brief, Propose, and Scaffold modes?▼

Brief mode returns a ready-to-use project brief only. Propose mode inspects context and proposes the scaffold without editing files. Scaffold mode creates or updates the local project, but never pushes, deploys, or touches external systems unless explicitly requested.

What tech stack does the default web project scaffold use?▼

The default stack is Next.js App Router with React and strict TypeScript, Tailwind CSS with OKLCH tokens, shadcn/ui-style components, Supabase for backend, Vercel hosting, and Bun as package manager. Existing repository conventions and recorded exceptions override these defaults.

Can I use this for non-web projects?▼

Yes. For non-web projects the workflow uses the ecosystem and commands named in the brief or already established by the repository, and it does not force the web stack onto them.

When should I use workspace-setup directly instead of this workflow?▼

Use workspace-setup directly for workspace-only review, repair, or migration of an existing project. Use the quickstart workflow when starting, scaffolding, or bootstrapping a project from intake through first operable state.