AlexPEClub

Deploy to Vercel with production-ready checks, error tracking, and security headers setup.

Write a full feature spec for a feature. Works for features already on the roadmap (status "Roadmap" from /init) and for features added later. Pass a feature name or PROJ-X ID as argument.

Design PM-friendly technical architecture for features. No code, only high-level design decisions.

Always use when the user wants to discuss an exsiting feature or specification. Open an existing feature spec to improve, extend, or fundamentally challenge it. Pass the feature ID as argument (e.g. /refine PROJ-2).

Build UI components with React, Next.js, Tailwind CSS, and shadcn/ui. Use after architecture is designed.

Initialize a new project. Creates the PRD and a prioritized feature map. Run once at the very start of a new project. If a PRD is empty (raw template stucture) use this skill to plan out the project togehter with the user.

Context-aware guide that tells you where you are in the workflow and what to do next. Use anytime you're unsure.

Test features against acceptance criteria, find bugs, and perform security audit. Use after implementation is done.

Design PM-friendly technical architecture for features. No code, only high-level design decisions. Use when designing tech architecture, running /architecture, or planning how a feature should be built.

Build APIs, database schemas, and server-side logic with Supabase. Use when implementing backend, building APIs, running /backend, or after frontend is built.

Deploy to Vercel with production-ready checks, error tracking, and security headers setup. Use when deploying, running /deploy, or preparing for production.

Build UI components with React, Next.js, Tailwind CSS, and shadcn/ui. Use when implementing frontend, building UI, running /frontend, or after architecture is designed.

Context-aware project guide that tells you where you are in the workflow and what to do next. Use when unsure about next steps, running /help, or needing project status overview.

Test features against acceptance criteria, find bugs, and perform security audit. Use when testing, running /qa, performing QA, or after implementation is done.

Create detailed feature specifications with user stories, acceptance criteria, and edge cases. Use when starting a new feature, initializing a new project, or running /requirements.