engineering-standards-builder

Audits project code, configuration, and CI to generate persistent engineering standards skills.

2|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/NAMEWTA/learning-open-code --skill engineering-standards-builder-namewta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: engineering-standards-builder
Source: https://github.com/NAMEWTA/learning-open-code/tree/main/speculo/skills/engineering-standards-builder
Command: npx skills add https://github.com/NAMEWTA/learning-open-code --skill engineering-standards-builder-namewta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Teams lack a systematic way to turn an existing codebase's real conventions into reusable, agent-readable engineering standards. This Skill audits the current project's code, directory layout, configuration, tests, CI, and templates, then compiles the evidence into a persistent project-specific Skill Set under .agents/skills/ instead of copying generic best-practice boilerplate. ## Core Features & Use Cases - Deterministic Project Discovery: A read-only scanner builds a project inventory covering languages, frameworks, build systems, test setups, and CI commands for TypeScript/JavaScript, Java, Go, and Rust projects. - Evidence-Based Skill Generation: Produces a root engineering-standards router Skill plus optional domain Skills, with an ownership manifest (generated-skill-set.json) so refreshes only touch Builder-owned files. - Validation and Self-Testing: Ships validators that check generated Skill Sets against project signals, plus fixture-driven self-tests covering Vue, React, Spring Boot, Go, Rust, and polyglot monorepos. - Use Case: Point it at a polyglot monorepo with a Vue frontend, Spring Boot services, and a Go worker; it detects each module's stack, converges conflicting conventions, and generates a minimal Skill Set that routes future AI coding sessions to the right project-specific rules. ## Quick Start Ask the agent to run the engineering-standards-builder skill to audit this repository and generate the project engineering standards Skill Set under .agents/skills/.

Frequently Asked Questions about engineering-standards-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate engineering standards from an existing codebase?▼

Invoke the engineering-standards-builder skill explicitly in your project. It runs a read-only discovery scanner, audits code, tests, CI, and templates as evidence, then writes a root engineering-standards Skill plus optional domain Skills into .agents/skills/.

What languages and frameworks does the project scanner detect?▼

The scanner detects TypeScript, JavaScript, Vue, React, Java with Maven or Gradle, Spring Boot, Go modules, and Rust Cargo workspaces. Other languages such as Kotlin fall back to a generic adapter contract rather than a wrong language profile.

Does the builder overwrite my existing custom skills?▼

No. It records every path it owns in generated-skill-set.json and only updates or deletes those registered paths on refresh. Skills outside the manifest are treated as user-maintained and left untouched.

Can it run automatically when I open a new project?▼

No. The skill sets disable-model-invocation to true, so it only runs when the user explicitly calls it. It never auto-starts or copies its generic references into a project as standards.

How do I validate the generated skill set?▼

Run node scripts/validate-generated-skill.mjs --root <project-root> --strict. It checks ownership, frontmatter, router links, project source references, and rejects generated language or framework rules that lack matching project signals.

When does it create separate domain skills instead of one router?▼

A domain Skill is created only when it has an independently triggerable scenario, repeated reuse, sufficient project evidence, a clear boundary from the root router, and a real reduction in irrelevant context. Otherwise content stays in the root engineering-standards Skill.