New project docs
These are the current Howells project defaults:
- the bundled UI baseline for shared UI, tokens, motion, and Storybook
- native coding-assistant workflows and Matt Pocock's skills for general software development
- the independent skills collection for specialist work that should not live inside one product repo
@howells/lintfor pinned Oxlint/Oxfmt linting and formatting@howells/typescript-configfor thin, explicit tsconfig presets@howells/envyfor typed env parsing and deployment env checks@howells/ai, Mastra, and deliberately scoped MCP packages for AI-capable product and agent work- Motif's SDK and agent-readable CLI for image generation, image editing, utility media tools, and creative automation
- conservative Turborepo defaults through the root
turbo.jsonsnippet
Defaults
- Default repo shape:
pnpmmonorepo, usually withapps/*andpackages/* - Default UI stack: Next.js App Router, React, Tailwind CSS v4, Base UI, and Storybook when the repo exports reusable UI; unified Radix is the deliberate opt-out
- Default linting and formatting: prefer the
@howells/lintOxlint/Oxfmt lane - Default task runner: Turborepo with cache disabled until a repo proves it is deterministic
- Default data stack for product apps: Drizzle and Neon, with the narrowest typed API boundary that fits and React Query when client server-state exists
- Default AI-capable shape: shared provider baseline through
@howells/ai, image generation through Motif, product orchestration through repo-localaioragents, and MCP in its own package only when the product needs that protocol surface
Sections
- Principles
- Getting Started
- Stack Decisions
- Architecture Defaults
- Repo Archetypes
- Package Boundaries
- Deployment Defaults
- Default Dependencies
- Config Snippets
- UI Projects
- Shared Package Candidates
- Agent Workflow
- Development Skills
- Worktree Coordination
- Agentic Development
- Launch Checklist
Agent skill
The Project Docs are the source of truth. The installable skill at skills/scaffold is a distribution surface that routes supported coding assistants through these docs without loading every reference at once.
What this standard optimises for
- Low config drift across active repos
- Fast project setup without re-deciding toolchain basics
- Correctness over cleverness
- Shared UI primitives without flattening project identity
- Short agent instructions that prevent ambiguity and drift
- Reusable skills that stay independent when they solve cross-repo agent problems