Build day. Pick one thing and ship it.

Apply my brand to this design system - use my logo, colours and fonts, and keep the structure and templates. Here's my brand: [attach your assets if you haven't already / name your colours / name your fonts]. Update every asset so it's on-brand. If anything's missing, ask me before guessing.

Add all of the social posts from the linked AI Champions Club brand design to a new page in my brand design system. Include every supplied social-post format and layout, but restyle each one using my logo, colours, fonts, imagery and brand voice. Keep the original dimensions and make every template editable and reusable. Do not leave any of the supplied social-post templates out.

Can we please create a new marketing campaign for the socials for my business? The target market is [X]. The campaign I want to run is [Y]. Use my design system so everything is on-brand.

Set up this website project and prove the starter works. Install the required packages, run the production build, fix any setup errors, then start the local development site for me. Give me the local URL to open. I should see the generic “Your Business” website. Explain what you do in plain English and ask before making any major change.

Use $website-kickoff to configure this website for my business. Interview me a few questions at a time. Suggest sensible defaults when I do not know, but never invent proof or business facts. Show me the business brief and route plan before you change the starter site, then continue until the production build passes.

Use $website-kickoff to configure this website for my business. My existing website is https://YOUR-DOMAIN-HERE.com. Inventory its public pages and reuse the useful facts, URLs and content structure. Confirm anything stale or uncertain, interview me only about gaps, and show me the business brief and route plan before implementation. Then continue until the production build and placeholder scan pass.

The brief is close, but change [specific fact]. Remove [page] because we cannot make it useful yet. Add [offer/audience] and use [tone]. Keep [existing URL] because it already has traffic. Update the three kickoff files, show me the revised route plan, then implement it.

Run the full website-kickoff verification now. Build every route to static HTML, check titles, descriptions, H1s, canonicals, sitemap membership, internal links, noindex pages, mobile navigation, forms and remaining starter markers. Fix every code or content-structure failure you can. Then give me the local preview command, deployment settings, route list, environment variables, publishing instructions and only the factual assets or approvals that still require me.

Build the finished website and start a local production preview for me. Fix any build errors you find, then give me the preview URL to open.

Initialise a git repo here, add a sensible .gitignore for a Node/Vite project, commit everything, then create a new private GitHub repo called bobs-website and push to it using the gh CLI.

Let's keep improving the app. Next I'd like: [describe one change in plain words].
Remember I'm not a software engineer - explain what you're doing simply.
Make one small change at a time, tell me which files changed and how to check it in the browser,
and stop to ask me before anything risky.

I have created an empty private GitHub repository at:
<PASTE YOUR REPOSITORY URL HERE>

Please:
- Initialise git in this project if it is not already.
- Make sure a sensible .gitignore is in place (node_modules, .env, the local SQLite file).
- Create a first commit.
- Add that GitHub repository as the remote named "origin".
- Push the code to the main branch.

After each step, explain in plain English what you just did and why - assume I'm not a developer. Stop and ask me before anything needs my GitHub login.

I have installed the Railway CLI and run `railway login`.

Please set up a Postgres database for this app on Railway:
- Create a new Railway project and add a Postgres database to it.
- Switch this app's Prisma datasource from SQLite to Postgres.
- Wire up the DATABASE_URL from Railway, run the migrations, and keep my existing tables and seed data.
After each step, explain in plain English what you just did and why - assume I'm not a developer. Stop and ask me before anything needs a login or could cost money.

Now deploy this Next.js app to Railway using the Railway CLI:
- Deploy it into the same Railway project as the Postgres database.
- Configure the build and start commands correctly for a Next.js app.
- Make sure the app connects to the Railway Postgres database via DATABASE_URL.
- Give me the public URL once it is live.
After each step, explain in plain English what you just did and why - assume I'm not a developer. Stop and ask me before anything needs a login or could cost money.

Set up a proper production deploy for this app on Railway, then wire up automatic deploys from GitHub.
- Create a separate Railway production environment, kept apart from my day-to-day setup.
- Add a GitHub Action that automatically deploys to Railway production whenever I push to the prod branch.
- Commit and push the workflow and any config to my GitHub repo.
After each step, explain in plain English what you just did and why - I'm not a developer. Stop and ask me before anything needs a login or could cost money.

Review this codebase for security holes before real users touch it.
- Find common vulnerabilities: injection, exposed secrets or API keys, insecure dependencies, and missing input validation.
- Set up proper authorization: a logged-in user must only be able to see and change their OWN data, and must not be able to call API endpoints or perform actions they aren't allowed to. No endpoint should be usable just because someone knows the URL.
- Review the API against the OWASP API Security Top 10 and tell me exactly where it falls short.
List what you find by severity, fix what you can safely fix, and flag anything that needs my decision or a real developer.

Before doing anything for real, do a dry run of this agent.
Show me exactly what you WOULD do, step by step, without sending, changing or deleting anything:
- what you read, and the items you found
- what you'd draft or produce for each
- anything you'd touch that I should know about
Then wait for me to review it against the role and guardrails before we ever run it for real.

Use the setup-marketing-bench skill and interview me in short rounds.
Help me define the company, offers, audience, brand voice, visual direction,
channels, capacity, budget, KPI definitions and approval rules.
Update the foundation files, then run the readiness checker.
Label assumptions and leave TODOs for anything we cannot answer yet.

Create a paid ad campaign for [offer]. Read the foundation files first.
Decide with me whether Google or Meta fits this offer and audience better.
Copy the matching campaign template under 03-paid/, then use the
creative-production skill to adapt ad-mockups.html and ad-mockups-new.html
to our brand. Complete the brief, creative, targeting, budget, launch
checklist and stop conditions. Give me the ad copy, headlines and
exact-size creative. Keep every status as Draft and the campaign paused -
do not launch, activate or spend anything.

Now create a small organic social campaign for the same offer.
Use the post template and the creative-production skill. Adapt the
editable social-card templates to our brand. Give me platform-specific
copy, square and story/reel designs, alt text, UTMs, an asset manifest
and a review checklist. Keep every status as Draft.

Review both campaigns against the playbook and foundation files.
For the paid campaign, confirm the Google or Meta brief, targeting, budget,
tracking and stop conditions, and show the exact account and actions that
would create it paused. For organic, prepare the Buffer queue and run
validation in dry-run mode. Show me every account, content, date/time,
timezone, budget and action that would happen next.
Do not publish, launch, activate or spend anything.