Closing the intent-to-code chasm - specification-driven development with BDD verification chain

Quickstart example: Express.js API coding standards (rules)

Gemini Enterprise A2A configuration and rules.

Decision-Linked Development (DLD) — a workflow for recording, linking, and maintaining development decisions alongside code. Skills for planning, recording, implementing, auditing, and documenting decisions via @decision annotations.

Security rules for untrusted NanoClaw groups. Credential protection, internal file protection, social engineering defenses.

Run quality checks on Java code before committing. Validates against best practices, enterprise standards, and common issues.

designing a new programming language

Discover and apply best practice skills automatically. Gap analysis scans the codebase, skill-search fills gaps from the registry, skill-classifier separates proactive from reactive skills, quality-standards generates CLAUDE.md guidance, self-review compares code against checklists, and verification-strategy sets up test/lint/typecheck feedback loops.

Rules for trusted NanoClaw groups. Shared memory, session bootstrap, cross-group memory updates. Loaded for trusted and main containers only.

Automatically monitor GitHub Actions workflows after git push operations. Tracks workflow progress and reports pass/fail results.

A test plugin with rules, skills, and commands

Tessl CLI MCP tool usage guidelines

Tessl CLI MCP tool usage guidelines

Spec-driven workflow covering requirement gathering, spec authoring, implementation review, and verification — with skills, rules, and evaluation scenarios.

Skills and rules for the NanoClaw host agent (Claude Code on Mac). Tile promotion, container management, staging checks, and reconciliation.