Keep editing forever

The site is yours. No monthly fee, no platform lock-in, no export friction. From here on you are in a loop:

1. Describe a change to your AI in plain language.
2. Let it make the change.
3. See the result on the local dev server (and after deploy, on your live site).
4. Iterate.

Most days, that is the whole job.

Common next moves

These are bundled inside the kit. Just say the trigger phrase to your AI:

• "Add Google Analytics." → see Add analytics
• "Make the contact form actually send emails." → see Wire the contact form
• "Run an SEO pass across every page." → see Add SEO
• "Check accessibility on my site." → see a11y audit
• "Run a Lighthouse pass and fix easy wins." → see Performance audit
• "Add a new service / case study / page." → see the What you can ask your AI tables.

For backing up your code so a laptop crash does not cost you everything, see Backing up your work.

Pull in bigger capabilities

For things outside the bundled set — auth, database, payments, AI image generation, copywriting help, conversion optimization, scraping, animations — there is a curated catalog of agent skills you can pull in. Browse the full list at Extending with other tools, grouped by what you are doing.

Skills are reusable capabilities for AI agents. They provide procedural knowledge that helps agents accomplish specific tasks more effectively. Think of them as plugins or extensions that enhance what your AI agent can do.

Three ways to install a skill

1. Follow the skill's own page (recommended). Every skill page tells you how to install it. On officialskills.sh each skill has a copy-paste install command at the top — usually claude plugin marketplace add ... or similar. On GitHub-hosted skills, the README spells out the steps. Open the page, copy the command, run it from your project root.

2. Ask your AI to install it. Paste the skill page URL into your AI chat:

Install this skill into our project: <skill-url>

The AI opens the page, reads the install instructions, and runs them for you. Works for both registry and GitHub skills.

3. Do it yourself by hand. Download the skill files and place them in a folder. Two folder options:

• Tool-specific (auto-pickup): use the path your AI tool expects.

  Tool	Skills folder
  Claude Code	.claude/skills/<name>/
  Codex	.agents/skills/<name>/
  Cursor	.cursor/skills/<name>/
  Gemini CLI	.gemini/skills/<name>/
  Antigravity	.agent/skills/<name>/
  GitHub Copilot	.github/skills/<name>/
  OpenCode	.opencode/skills/<name>/
  Windsurf	.windsurf/skills/<name>/

• Generic (any tool): keep them all in one folder at the project root, for example external-skills/<name>/. Then in your AI chat, point at the file:

  I just added a new skill at external-skills/<name>/SKILL.md. Read it and use it for the next task whenever it applies.

  This works with every AI tool, including web chat (where you would paste the SKILL.md content into the conversation directly).

All three options are spelled out in Extending with other tools.