OPEN-SOURCE ENGINEERING TOOLKIT

Engineering guardrails for AI coding agents.

44 skills. Security audits. Accessibility checks. Repeatable engineering practices.

Give agents a structured way to build for the real world—with shared standards, explicit workflows, and checks that make important requirements verifiable.

Framework-agnostic Zero-dependency site MIT licensed

44reusable skills
08lifecycle stages
0site runtime dependencies
MITopen-source license

BUILT FOR THE WHOLE DELIVERY CYCLE

Good output is designed.
Quality is verified.

Guidance helps an agent choose a better implementation. Engineering checks help a team see whether selected requirements were actually tested.

01 / SECURITY

Security pattern audit

A zero-dependency Node.js scanner checks Markdown code examples for risky patterns such as eval(), unsafe HTML insertion, and wildcard message origins.

Inspect the audit ↗

02 / ACCESSIBILITY

Accessibility in CI

Playwright keyboard and focus regression tests cover skip links, form errors, and dialog focus behavior. An on-demand browser checker adds axe-core scans.

Explore accessibility tests ↗

03 / AGENT SKILLS

44 / SKILLS

Reusable engineering knowledge

Portable, task-focused skills cover design, frontend engineering, motion, accessibility, security, performance, and browser QA.

Browse all skills ↗

04 / DELIVERY SYSTEM

  1. 01 Foundation
  2. 02 Design
  3. 03 Frontend
  4. 04 Motion
  5. 05 Accessibility
  6. 06 Security
  7. 07 Performance
  8. 08 QA & release

An eight-stage lifecycle

Connect the work from repository foundations and design direction through implementation, verification, and release readiness.

View the architecture ↗

A SMALL, PRACTICAL DIFFERENCE

From plausible markup
to native semantics.

Skills provide implementation guidance. The rendered result still needs review and testing.

Raw AI output

FRAGILE

A clickable container needs custom keyboard and focus behavior.

<div
  class="button"
  onClick={handleSubmit}
>
  Submit
</div>
  • No native button semantics
  • No built-in keyboard activation
  • Focus behavior must be added

WebCraft Pro guidance

SEMANTIC

Use a native button and let the platform provide expected behavior.

<button
  type="submit"
  aria-label="Submit form"
>
  Submit
</button>
  • Native button semantics
  • Keyboard activation built in
  • Accessible name is explicit

For visible button text, that text normally supplies the accessible name; use aria-label when a control has no visible text or needs a more specific name.

MAKE THE STANDARD REPEATABLE

Don't just prompt for quality.
Build a way to verify it.

Explore the skills, inspect the checks, and adapt the workflow to the stack you already use.