End-to-end project setup for Claude Code and Claude app.

# Project Instructions

## Project goal

This repo is an end-to-end product project. Claude should help with product planning, design, implementation, SEO, QA, launch, and iteration.

## Workflow owner

Default engineering workflow:
- Use Superpowers for planning, implementation, testing, and review.
- Use Caveman for concise communication during coding.
- Do not use Caveman Ultra for design, UX, copywriting, product strategy, legal review, or marketing strategy.
- Use Cavecrew only for focused investigation, review, or isolated edits.

## Skill routing

### Product and planning
Use product-discovery or project docs when defining:
- target user
- problem
- MVP
- feature scope
- launch plan

### Design
Use frontend-design and selected design skills when working on:
- landing pages
- dashboards
- UI components
- visual hierarchy
- spacing, typography, color, layout
- mobile responsiveness

Before coding major UI, produce a compact design plan:
- audience
- page job
- visual direction
- typography
- palette
- layout
- key components
- anti-generic critique

### Development
Use Superpowers as the main workflow for:
- feature implementation
- refactors
- tests
- architecture decisions
- debugging

### Browser QA
Use agent-browser whenever UI behavior or visual correctness matters.
Verify changes in the browser before claiming completion.

### SEO
Use claude-seo for:
- technical SEO
- metadata
- schema
- content quality
- local SEO
- international SEO
- launch audits

Use marketingskills for:
- conversion
- copywriting
- landing page persuasion
- funnel improvements
- analytics/event ideas

### Legal and compliance
Do not give final legal conclusions.
Use legal-risk-review only to identify issues to verify:
- privacy
- cookies
- terms
- refunds
- user data
- regulated claims
- AI-generated content
- open-source licenses

### Social and launch content
Use social/content skills for:
- launch posts
- LinkedIn content
- newsletter drafts
- content repurposing
- voice consistency

## Conflict rule

User request > project CLAUDE.md > active slash command > skill defaults.

Only one high-level workflow should own the task at a time.
If two skills overlap, choose based on the routing above.

## Output expectations

For every substantial task:
- state what changed
- mention files edited
- mention tests or browser checks run
- mention remaining risks or TODOs

# Ongoing Project Retrofit Instructions

## First task before changing code

Before implementing new features, audit the existing project.

Produce:
- docs/project/current-state.md
- docs/project/architecture.md
- docs/project/risk-list.md
- docs/project/setup-notes.md

## Audit checklist

Inspect:
- framework and package manager
- app routes/pages
- data model and persistence
- auth and permissions
- environment variables, without reading secrets directly
- deployment setup
- tests and scripts
- styling system
- SEO metadata
- analytics/tracking
- error handling
- accessibility and responsive behavior

## Rules

- Do not rewrite the architecture unless there is a clear reason.
- Prefer small, reversible changes.
- Preserve existing conventions unless they are actively harmful.
- Before editing, explain the smallest safe plan.
- After editing, run the relevant checks.
- If UI is changed, verify with agent-browser.

# Design Phase Instructions

## Goal

Create interfaces that look intentional, modern, and production-ready. Avoid generic AI-generated UI.

## Use these skills

- frontend-design
- ui-design
- design-systems
- interaction-design
- visual-critique

Do not use Caveman Ultra during this phase.

## Design plan required before coding

For each major page or flow, produce:
- target audience
- page job
- emotional tone
- layout structure
- typography direction
- color palette direction
- spacing rhythm
- primary components
- mobile behavior
- one signature visual detail
- anti-generic critique

## Implementation expectations

- Use the existing design system if present.
- If no design system exists, create minimal tokens for spacing, radius, type scale, and colors.
- Make mobile excellent, not just acceptable.
- Use real copy, not lorem ipsum, when possible.
- Verify important UI states in the browser.

## Output

Create or update:
- docs/design/design-direction.md
- docs/design/component-system.md
- screenshots or browser QA notes when useful

# Launch, SEO, and Conversion Instructions

## Goal

Prepare the product for launch with clear messaging, strong technical SEO, and conversion-focused pages.

## Skill routing

Use claude-seo for:
- technical SEO
- metadata
- schema
- sitemap/robots checks
- canonical URLs
- structured data
- content quality
- local/international SEO when relevant

Use marketingskills for:
- positioning
- headlines
- offer clarity
- objections
- CTAs
- pricing page logic
- funnel improvements
- analytics/event ideas

Use agent-browser for:
- checking the live or local page
- screenshots
- mobile viewport review
- form and CTA verification

## Required outputs

Create or update:
- docs/marketing/seo-audit.md
- docs/marketing/conversion-review.md
- docs/marketing/launch-checklist.md

## Launch checklist

Verify:
- page titles and meta descriptions
- Open Graph and social previews
- schema markup when useful
- sitemap and robots policy
- canonical URLs
- favicon and manifest
- analytics/events
- form success/error states
- mobile layout
- page speed basics
- privacy/cookie links when needed

I am starting an end-to-end product project.

Help me define:
1. target user / ICP
2. painful problem
3. current alternatives
4. sharp positioning
5. offer
6. MVP scope
7. non-goals
8. landing page angle
9. launch channels
10. obvious legal/privacy risks to verify

Output the result as files I can later create in my repo:
- docs/product/idea.md
- docs/product/icp.md
- docs/product/positioning.md
- docs/product/offer.md
- docs/product/mvp-scope.md
- docs/marketing/content-angles.md
- docs/legal/legal-risk-notes.md

We are configuring this project for end-to-end development.

First, read the repo structure and create a compact project map.
Do not make code changes yet.

Then produce:
- docs/project/current-state.md
- docs/project/architecture.md
- docs/project/setup-notes.md
- docs/project/next-steps.md

After that, propose the smallest safe next task.
Use the CLAUDE.md routing rules for skills and workflows.

# Skill Installation Checklist

## Claude Code / terminal agent

Core:
- Superpowers
- Caveman
- Cavecrew

Design:
- Anthropic frontend-design
- Owl ui-design
- Owl design-systems
- Owl interaction-design
- Owl visual-critique

Execution and QA:
- Vercel agent-browser

Marketing and SEO:
- marketingskills
- claude-seo

Optional later:
- claude-ads
- small custom legal-risk-review skill
- GStack in a separate test project only

## Claude app

Strategy and content:
- social-media-skills voice-builder
- social-media-skills post-writer
- social-media-skills profile-optimizer
- marketingskills

Legal/compliance review:
- claude-for-legal only when needed

Design strategy:
- frontend-design or selected design skills if useful

## Do not install by default

- Full Owl suite
- Full claude-for-legal inside every repo
- claude-ads before there is validation or campaign data
- GStack as the default workflow