- Set up spec-kit framework (checklist, decisions, scripts)
- Created project documentation (README, discovery questionnaire)
- Configured CI compliance checks
- Ready for discovery phase and client input
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
35 lines
1.6 KiB
Markdown
35 lines
1.6 KiB
Markdown
# 1000planets.cloud Marketing Site - Spec Kit
|
|
|
|
This folder defines the **Spec Kit** development framework for the 1000planets.cloud marketing site. It documents compliance goals, decision records, and support artifacts so every change can be judged against the same standards.
|
|
|
|
## Sections
|
|
|
|
- `checklist.md`: High-level requirements that must be satisfied before a release or feature is merged.
|
|
- `decisions/`: ADR-style writeups capturing architectural choices (tech stack, design system, deployment strategy, etc.).
|
|
- `scripts/ci-checks.sh`: Quick verification script for local or CI execution to assert basic compliance.
|
|
- `project-plan.md`: Pre-flight record listing features, phases, owners, and blockers.
|
|
|
|
## How to Use It
|
|
|
|
1. **Read the checklist** before starting work to understand expectations.
|
|
2. **Record any substantial decision** in a new decision file inside `decisions/`.
|
|
3. **Update `project-plan.md`** whenever you begin a new feature or phase.
|
|
4. **Run `bash spec-kit/scripts/ci-checks.sh`** before submitting changes.
|
|
|
|
## Project Vision
|
|
|
|
This is the forward-facing marketing site for 1000planets.cloud - showcasing our AI-powered automation platform with human-in-the-loop design. The site must:
|
|
|
|
- Inspire confidence through hypermodern design
|
|
- Emphasize cost savings through automation
|
|
- Communicate granular control (set-it-and-forget-it flexibility)
|
|
- Reflect a global, AI-forward mentality
|
|
- Convert visitors to qualified leads/demos
|
|
|
|
## Compliance Philosophy
|
|
|
|
Every feature should:
|
|
- Be documented before implementation
|
|
- Include decision rationale in `decisions/`
|
|
- Pass CI checks before merge
|
|
- Align with brand guidelines and user experience goals
|