Area guide · 30 packages · Find the owner of a command
CLI, authoring and agent tooling
Navigate the command host, source analysis, documentation generators and native agent-pack delivery used to work on ContractSpec projects.
What are you trying to do?
- Which package owns a CLI command?
- How are optional command packs discovered?
- Where do docs, skills and editor integrations get their context?
Why start with these packages
Suggested entry point
@lssm-tech/lib.cli-runtimeUse deterministic command-pack discovery, host ports and canonical workspace analysis/rendering leaves.
Suggested entry point
@lssm-tech/app.cli-contractspecInspect the actual CLI application that composes commands for users.
Suggested entry point
@lssm-tech/agentpacksExplore pack loading, target-specific configuration, skills and plugin export.
Suggested entry point
@lssm-tech/tool.docs-generatorInspect the Markdown/registry-to-reference-index generation stage.
Practical steps
Step 01
Trace one CLI action
Open the application entry and its command-pack declaration, then locate the owning implementation. Check whether the action reads, writes generated artifacts or requests a governed mutation before putting it into an automated workflow.
Step 02
Follow a generated document
Identify the authored spec/DocBlock or README, the producer, its output path and the loader that consumes it. Record which stage is stale and which dependencies should invalidate it.
Step 03
Prepare a coding-agent context path
Choose the installed host target and a focused skill. Link its required package/version references and example sources; keep retrieved evidence separate from trusted instructions and inspect the generated diff before applying configuration changes.
Find the command’s owner
CliRuntime supplies host construction and command-pack discovery. The documented discovery scope is the consumer’s direct dependencies and optionalDependencies whose package metadata declares a command pack. Include/exclude configuration selects packs, exclusion wins, and package-name ordering is deterministic. Selected packs are loaded before registration; conflicts are rejected before a pack changes the Commander program. Use this model to locate an optional AI, builder, design or examples command rather than assuming every command lives in the main CLI application.
Distinguish the generation stages
Workspace analysis owns source scanning, static diagnostics, semantic diff and Markdown/DocBlock rendering. The docs-generator tool is a separate stage that combines existing generated Markdown with the seeded registry to make a reference index. README-to-LLMS generation is another projection in web-landing. When documentation looks inconsistent, trace the particular producer and its inputs instead of rerunning an unrelated build. Preserve source paths and versions so diagnostics can lead an editor or agent to the real owner.
Choose the coding-tool target explicitly
Agentpacks merges configuration into host-specific rules, hooks, skills and other outputs for supported coding tools. Skills can include references and scripts; they should stay focused on a task and fetch version-appropriate context. The documented generate --diff path uses a non-writing overlay and reports drift. Successful writing generation has an additional RTK refresh behavior, so select the intended mode deliberately. Editor bridges and native plugin exports remain separate delivery surfaces whose supported features and versions need inspection.
Follow a practical path.
Trace one CLI action
Open the application entry and its command-pack declaration, then locate the owning implementation. Check whether the action reads, writes generated artifacts or requests a governed mutation before putting it into an automated workflow.
Follow a generated document
Identify the authored spec/DocBlock or README, the producer, its output path and the loader that consumes it. Record which stage is stale and which dependencies should invalidate it.
Prepare a coding-agent context path
Choose the installed host target and a focused skill. Link its required package/version references and example sources; keep retrieved evidence separate from trusted instructions and inspect the generated diff before applying configuration changes.
Packages in this area (30)
30 of 30 shown
- Open manual →
Canonical repository-local Claude, Codex, and agent guidance for ContractSpec consumers.
- Open manual →
Composable AI agent configuration manager. Pack-based rules, commands, skills, hooks, and MCP sync across OpenCode, Cursor, Claude Code, Codex, Gemini, Copilot, and more.
Explore pack loading, target-specific configuration, skills and plugin export.
- Open manual →
CLI tool for creating, building, and validating contract specifications
Inspect the actual CLI application that composes commands for users.
- Open manual →
Command-line database tooling for ContractSpec-managed schemas and operations.
- Open manual →
Multi-database command-line workflows for ContractSpec workspaces.
- Open manual →
Registry application for discovering and distributing ContractSpec agent packs.
- Open manual →
Registry server for ContractSpec packages, contracts, and ecosystem metadata.
- Open manual →
Biome presets, Grit plugins, and policy manifest for ContractSpec repositories.
- Open manual →
Workspace utilities for monorepo development
- Open manual →
Optional AI command pack for the ContractSpec CLI
- Open manual →
Optional Builder command pack for the ContractSpec CLI
- Open manual →
Optional design command pack for the ContractSpec CLI
- Open manual →
Optional examples command pack for the ContractSpec CLI
- Open manual →
Optional concrete AI providers and agents for ContractSpec workspace hosts
- Open manual →
Deterministic command-pack discovery and registration for ContractSpec CLI hosts
Use deterministic command-pack discovery, host ports and canonical workspace analysis/rendering leaves.
- Open manual →
Plugin API and registry for ContractSpec extensions
- Open manual →
Extract contract candidates from TypeScript source code across multiple frameworks (NestJS, Express, Fastify, Hono, Elysia, tRPC, Next.js)
- Open manual →
Owned TypeScript compiler API boundary for ContractSpec tooling
- Open manual →
Workspace discovery and management module
- Open manual →
Shared Bun build presets and CLI for ContractSpec packages
- Open manual →
Generator that walks ContractSpec defineCommand/defineQuery specs and produces MCP-compatible tool schemas.
- Open manual →
Generator that compiles ContractSpec defineDatabaseTable specs into Drizzle pgTable definitions, relations, and an RLS adapter manifest.
- Open manual →
CLI tool for creating ContractSpec plugins from templates
- Open manual →
CLI tool for generating docs artifacts from ContractSpec specs and DocBlocks
Inspect the Markdown/registry-to-reference-index generation stage.
- Open manual →
Build-time tool that prunes unreferenced translation catalog keys using RouteShardManifest reachability and t('key') source scanning
- Open manual →
Shared tsdown config presets for LSSM monorepo
- Open manual →
Pinned TypeScript tooling and shared compiler configuration for ContractSpec packages.
- Open manual →
Codemods + import-graph scanner that mechanically migrate consumers of the rich-reference legacy surfaces (CodeBlock, DiffBlock, ObjectReferenceHandler, RichContentReference, rich-code-preferences) to the post-S-8 surface (RichBlock, RichRef, RichReference, rich-reference/preferences).
- Open manual →
ESLint rules enforcing i18n hygiene: no module-scope translation calls and no raw Accept-Language reads.
- Open manual →
ESLint rule enforcing that every defineReferenceKind() call declares an explicit sensitiveFields array (closes F-4).
Curated but no longer in the workspace: app.cursor-marketplace, contractspec, jetbrains-contractspec-bridge, repo-scripts, spec-driven-development, vscode-contractspec
What connects to this area
Core contracts
Authoring commands operate on declared specs and their source conventions.
Agents and context
Coding tools need scoped context and explicit instruction authority.
Delivery and infrastructure
Source changes and generated artifacts enter existing quality/release workflows.
Examples and patterns
Command and editor flows should point to maintained examples.