<< All versions

Skill v1.0.1

currentAutomated scan100/100
stonega/harness/new-project

+6 new

──Details
PublishedOctober 25, 2026 at 10:41 PM
Content Hashsha256:5927d0d2bc04c255...
Git SHA335ae358f181
Bump Typepatch
Compare with v1.0.0
──Files
Files (1 file, 5.3 KB)
SKILL.md5.3 KBactive
SKILL.md · 76 lines · 5.3 KB

version: "1.0.1" name: new-project description: Bootstrap a new project from this harness, including repo layout, project-specific AGENTS instructions, starter documentation, and the default app stack. Use whenever the user wants to create, scaffold, initialize, or structure a new repo, especially when they mention Bun, Expo, React Router, Hono, Cloudflare, Ink, theme-aware TUIs, native GNOME apps, GNOME Shell extensions, monorepos, standalone apps, or "start a new project" without a fully specified setup.


New Project

Quick start

Turn a rough product request into an initialized repo with a justified layout, a project-specific AGENTS.md, starter docs, a minimal default stack, and Biome as the default linter/formatter unless the user asked for alternatives.

Defaults: Bun for package management and workspaces, Biome for linting and formatting, React Router v7 for web, Expo for mobile, Hono for backend, Cloudflare for deployment, Bun + Ink with theme awareness for TUI, and GJS + GTK 4 + libadwaita for native GNOME apps.

Read WEB.md only for web apps. Read MOBILE.md only for mobile apps. Read TUI.md only for terminal interfaces. Read GNOME.md only for native GNOME apps or GNOME Shell extensions.

For projects with a user interface, read design.md before planning screens or choosing UI patterns. Adapt the applicable preferences into docs/design/ui-rules.md and link it from the generated AGENTS.md.

Workflow

  1. Infer the smallest viable shape.
  • Prefer standalone for one deployable surface.
  • Prefer a monorepo for multiple apps, shared packages, or separate deployment targets.
  • If the request is vague, choose the smallest structure that will not block the likely roadmap.
  1. Build AGENTS.md before the rest of the repo.
  • First fetch https://raw.githubusercontent.com/stonega/harness/refs/heads/main/_AGENTS.md.
  • Adapt it to the actual project structure, commands, and testing workflow.
  • For GNOME Shell extensions with panel menus, include the popup alignment rules.
  • If the remote file is unavailable, use the local harness copy and say so.
  1. Create the base structure.
  • Always create README.md, AGENTS.md, docs/design, docs/implementation, docs/user, scripts, examples, and postmortem.
  • For monorepos, use apps/ for deployable apps and packages/ for shared code.
  1. Initialize Bun first, add Biome, and keep dependencies explicit. For GNOME projects, use Bun for development tooling; native apps run with GJS and extensions load inside GNOME Shell.
  2. Choose the scaffold by surface.
  • Web: React Router Latest.
  • Backend: Hono on Cloudflare.
  • Mobile: Expo.
  • Web + backend: separate apps in one repo.
  • Web + mobile + backend: apps/web, apps/mobile, apps/backend.
  • TUI: use Bun + Ink and make the interface theme-aware.
  • GNOME app: use GJS ES modules with GTK 4 and libadwaita; add a Shell extension only when desktop integration requires it.
  • GNOME Shell extension: follow GNOME.md for extension metadata, lifecycle, and isolated testing; add a GTK app only when the product needs one.
  1. Write docs immediately.
  • Add docs/design/architecture.md with structure and rationale.
  • Add docs/implementation/setup.md with bootstrap and local-dev notes.
  • Update README.md with install, run, and test commands.
  1. Add baseline quality support.
  • Add deterministic tests for generated logic or scripts.
  • Add idempotent scripts when they simplify setup or repeated workflows.
  • Add examples when a new workflow or API is introduced.
  1. Apply stack-specific defaults only where needed.
  • Use WEB.md for web packages and setup.
  • Use MOBILE.md for mobile packages and setup.
  • Use TUI.md for Bun + Ink packages, executable setup, terminal theming, and tests.
  • Use GNOME.md for native runtime dependencies, desktop integration, Meson installation, and isolated GNOME tests.
  1. Initialize Git and create the first commit after setup.
  • Run the project's checks and ensure .gitignore excludes dependencies, build outputs, and local environment files before staging.
  • Run git init in the new project root unless it already has its own Git repository; reuse a repository created by the scaffold.
  • Stage the project files, review the staged changes, and run git commit -m "Initial commit". If the scaffold already created a commit, commit any remaining setup changes without rewriting history.
  • Verify the working tree is clean and report the resulting commit hash. If the commit cannot be completed, report the blocker.

Expected output

Leave the repo with a coherent layout, a project-specific AGENTS.md, starter docs, a runnable README, minimal dependencies, and the completed setup committed to Git.

Default layouts

Standalone: AGENTS.md, README.md, docs/, src/, tests/, scripts/, examples/, postmortem/ Monorepo: AGENTS.md, README.md, apps/, packages/, docs/, scripts/, examples/, postmortem/

Rules

  • Prefer standalone unless multiple independently deployed surfaces are clearly needed.
  • Keep generated AGENTS.md aligned with the actual repo structure.
  • Create documentation and tests as part of setup, not as a later cleanup pass.
← v1.0.0All versions