elias/everything-claude-code
1
0
Fork 0
mirror of https://github.com/affaan-m/everything-claude-code.git synced 2026-06-16 08:26:52 +08:00
Code Issues Packages Projects Releases Wiki Activity
everything-claude-code/skills/ai-first-engineering/SKILL.md
BERORINPO db7f2a6fd5 fix(skills): move top-level origin frontmatter key under metadata 
The official Agent Skills spec (agentskills.io/specification) whitelists exactly
6 top-level frontmatter keys (name/description/license/compatibility/metadata/
allowed-tools). A top-level `origin` key fails the official validator
(anthropics/skills quick_validate.py ALLOWED_PROPERTIES; skills-ref validate).

This moves `origin: X` -> `metadata.origin: X` across the canonical skills/
tree, preserving each value verbatim. Frontmatter-only, minimal diff.

- 251 SKILL.md updated (242 new metadata block, 9 appended to existing metadata)
- origin values preserved verbatim (verified 251/251)
- YAML validated on all changed files
- scoped to canonical skills/ only (docs/<lang> translations + tool mirrors
  .cursor/.kiro/.agents left untouched; presumably regenerated from canonical)

Addresses #2233
2026-06-11 21:12:21 +09:00

1.3 KiB
Raw Blame History

name, description, metadata
name description metadata
ai-first-engineering Engineering operating model for teams where AI agents generate a large share of implementation output.
origin
ECC

AI-First Engineering

Use this skill when designing process, reviews, and architecture for teams shipping with AI-assisted code generation.

Process Shifts

  1. Planning quality matters more than typing speed.
  2. Eval coverage matters more than anecdotal confidence.
  3. Review focus shifts from syntax to system behavior.

Architecture Requirements

Prefer architectures that are agent-friendly:

  • explicit boundaries
  • stable contracts
  • typed interfaces
  • deterministic tests

Avoid implicit behavior spread across hidden conventions.

Code Review in AI-First Teams

Review for:

  • behavior regressions
  • security assumptions
  • data integrity
  • failure handling
  • rollout safety

Minimize time spent on style issues already covered by automation.

Hiring and Evaluation Signals

Strong AI-first engineers:

  • decompose ambiguous work cleanly
  • define measurable acceptance criteria
  • produce high-signal prompts and evals
  • enforce risk controls under delivery pressure

Testing Standard

Raise testing bar for generated code:

  • required regression coverage for touched domains
  • explicit edge-case assertions
  • integration checks for interface boundaries