malty/1000planets-site
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
1000planets-site/spec-kit
History
fullsizemalt 673007cc9f Discovery complete: Creative brief and architectural decisions 
- Completed client discovery questionnaire
- Created creative brief with mission, brand essence, and strategy
- ADR 0001: Tech stack (Next.js 14, Tailwind, Sanity, self-hosted)
- ADR 0002: Brand guidelines (colors, typography, voice, accessibility)

Key insights:
- Social impact mission: /month for single mothers and underserved communities
- Visual: Linear + Vercel aesthetic with semantic color system
- Target: Small business owners with high Google rankings but poor sites
- Primary CTA: 30-day free trial with domain pointing

Ready to build!

🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
2025-12-11 12:23:51 -08:00
..
decisions Discovery complete: Creative brief and architectural decisions 2025-12-11 12:23:51 -08:00
scripts Initial commit: Spec Kit compliant project structure 2025-12-11 12:18:20 -08:00
checklist.md Initial commit: Spec Kit compliant project structure 2025-12-11 12:18:20 -08:00
project-plan.md Initial commit: Spec Kit compliant project structure 2025-12-11 12:18:20 -08:00
README.md Initial commit: Spec Kit compliant project structure 2025-12-11 12:18:20 -08:00

README.md

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