# skill.md — Solo Website (starter template from antist.ai)

> Skill-Centric Workflow: before writing any code, your agent fills this file in.
> During the project, the agent KEEPS UPDATING it — new pitfalls, changed plans, done/undone.
> Any future agent (or future you) reads this file first and continues seamlessly.
> Method & updates: https://antist.ai/methodology · contact: Antisubmissivist@gmail.com

---
name: <project-name>
description: <one line: what the site is and who it serves>
status: planning   # planning | building | live | maintaining
last_updated: <!-- agent: keep current -->
---

## 1. Goal & success criteria
- The site's single job: <what a visitor should be able to do>
- Success = domain serves 200 on all target locales, deploy = git push
- Budget tier: <zero | light <$10 | serious <$50>  (see https://antist.ai/scenarios/solo-website)

## 2. Architecture decision
- Chosen: <static | SSG | edge-fullstack | ...> because <one honest sentence>
- Rejected: <shapes you consciously skipped and why>
- Upgrade signal: <the concrete sign that means it's time to change shape>

## 3. Tech & tool stack (pin versions — agents love upgrading things that work)
| Layer | Choice | Version pin | Why |
|---|---|---|---|
| Framework | | | |
| Styling | | | |
| i18n | | | |
| Hosting | | | |
| Package manager | | | |
| Formatter/linter | | | |

## 4. Key paths & accounts
- Local source: <absolute path>
- Repo: <github url> (private?)
- Hosting account/project: <where + project name>
- Domain & DNS: <registrar, nameservers>
- Deploy method: <push-to-deploy? command?>

## 5. Red lines (violating these = production incident)
- No secrets in the repo — ever. Use the host's secret store.
- No runtime filesystem reads if deploying to edge/serverless (build-time only).
- Pin the framework major version; upgrade only after reading the adapter's changelog.
- <!-- agent: append project-specific red lines discovered the hard way -->

## 6. Known pitfalls (append as you hit them, with dates)
- <!-- example: 2026-07-09 CI-built artifact 500'd: fs.readdirSync at runtime; moved data to build-time JSON import -->

## 7. Roadmap & status
- [ ] Phase 0: scaffold + repo + deploy pipeline + domain serves Hello World
- [ ] Phase 1: design system + real homepage
- [ ] Phase 2: content/data layer
- [ ] <!-- agent: keep this honest — checked means VERIFIED, not "should work" -->

## 8. Verification checklist (run after every deploy)
- [ ] All locales return 200 (curl, not browser cache)
- [ ] Key content keyword present in HTML
- [ ] No errors in host's live logs for 5 minutes