AI项目模板目录

nanohype

A tool-agnostic template catalog for AI-focused projects. Each template is a self-contained, scaffoldable starting point — consumable by any scaffolding tool that reads the template contract.

New here?

• Building an AI client (Bedrock agent, Claude session, custom orchestrator) and want to ship software on this stack? Start with the Platform Reference and the per-repo AGENTS.md.
• Scaffolding a project locally? Start with the Quick Start guide — find the right template, scaffold it, and run it in under 2 minutes.

Templates

Templates span four engineering categories plus composable modules. Beyond engineering, the catalog also carries cross-functional templates and agent briefs for design, QA, product, marketing, sales, operations, and customer success — see Cross-Functional Templates below.

AI Systems

Applications

Infrastructure

Composable Modules

Cross-Functional Templates

Beyond engineering, the catalog ships templates and agent briefs for design, QA, product, marketing, sales, operations, and customer success. Examples: prd-template, test-plan, design-system, brand-guidelines, runbook, incident-postmortem, onboarding-playbook, proposal-template. Agent briefs (brief-*) scaffold structured instruction documents instead of static files — one per non-engineering persona.

See the catalog reference for the decision matrix and the full per-persona breakdown.

How It Works

Every template lives in templates/<name>/ and contains:

• template.yaml — declares metadata, variables, conditionals, and hooks per the template contract spec
• skeleton/ — the file tree to scaffold, with placeholder strings for variable interpolation
• README.md — when and why to reach for this template

Scaffolding tools read template.yaml, collect variable values from the user, and render skeleton/ with those values substituted for their declared placeholders. The contract is generic — no tool-specific coupling.

Composites

Pre-configured multi-template stacks in composites/:

Composites define which templates to scaffold, where to nest them, and how variables flow across templates. See the composite contract for the specification.

SDK

@nanohype/sdk is the reference implementation of the template rendering contract. Install it as a dependency to build your own scaffolding tool, CLI, MCP server, or CI pipeline on top of nanohype templates.

import { LocalSource, renderTemplate } from '@nanohype/sdk';

const source = new LocalSource({ rootDir: './nanohype' });
const { manifest, files } = await source.fetchTemplate('agentic-loop');
const result = renderTemplate(manifest, files, { ProjectName: 'my-agent' });
// result.files — rendered SkeletonFile[] ready to write to disk

The SDK lives at sdk/ in this repo. See the Consumer Implementation Guide for the full scaffolding algorithm.

Docs

• Consumer Implementation Guide — scaffolding algorithm, composite orchestration, catalog integration
• Catalog Reference — decision matrix, composition map, and template selection guide
• Template Contract — the formal schema for template.yaml
• Composite Contract — multi-template stack manifests
• Authoring Guide — practical walkthrough for creating new templates
• Contributing — how to add a template or composite to the catalog

Reference Architectures

• Agentic Systems
• RAG Pipelines
• MCP Ecosystem

Diagrams

• Template Lifecycle
• Agentic Loop
• MCP Topology
• RAG Pipeline

Validation

npm install
npm run validate:schema

Or validate a single template:

./scripts/validate.sh templates/go-cli

License

Apache 2.0