Ai first engineering
Skill khanhhuyenngo985-sys/character-scene-design-skills/skills/.archive/ECC-ai/ai-first-engineering
通用角色与场景设计技能包:角色资产、身高比例锁、三视图一致性、服装状态、道具锚点、场景动线与 AI 图像/视频提示词流程
npx -y skills add khanhhuyenngo985-sys/character-scene-design-skills --skill ai-first-engineeringAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Engineering operating model for teams where AI agents generate a large share of implementation output.
SKILL.md
1.3 KB, as published. Nobody here has run it
AI-First Engineering
Use this skill when designing process, reviews, and architecture for teams shipping with AI-assisted code generation.
Process Shifts
- Planning quality matters more than typing speed.
- Eval coverage matters more than anecdotal confidence.
- 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