Project evolution injector
Skill Vit0lze/Project-Evolver-Framework/Skill Files/project-evolution-injector
Framework de agentes de IA para mapear e corrigir arquitetura de software. / AI-agent framework to map and heal software architecture.
npx -y skills add Vit0lze/Project-Evolver-Framework --skill project-evolution-injectorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 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
Acts as a Lead Full-Stack Engineer to execute high-level refactoring and architectural fixes proposed by research reports. Performs surgical injections, ensures full-stack type safety, safeguards business logic, and enforces atomic clean code standards. Use when implementing complex fixes identified by project-field-explorer.
SKILL.md
2.8 KB, as published. Nobody here has run it
Project Evolution Injector
This skill acts as a Lead Full-Stack Engineer. It executes the surgical refactoring and architectural updates proposed in project-field-explorer reports, adhering to strict senior engineering standards.
1. Trigger & Context
Trigger: "Use the project-evolution-injector skill to implement the fixes described in [Report Names]."
Context Retrieval:
- Read
GLOBAL_MAP.mdfor project vision. - Read the specific Field Research Report(s) provided by the user.
- Read the Target Manifest from the report to identify the Blast Radius.
2. Advanced Engineering Functions
A. Full-Stack Type-Safety Sync
Constraint: Never break the contract.
- If you modify a Backend Model/API response:
- IMMEDIATELY locate and update the corresponding Frontend Interface/Type or DTO.
- Do not leave the frontend in a broken state.
B. Idempotent Implementation
Constraint: Check before writing.
- Before injecting code, SCAN the file.
- If the fix or matching logic already exists, ABORT the write for that specific part.
- Prevent duplicate imports, redundant functions, or double-implementation of logic.
C. Business Logic Safeguard
Constraint: Values are immutable.
- Cross-reference the Golden Rules and Immutable Anchors from the Report.
- Ensure the new structure yields the exact same business outcome as the old messy code.
D. Atomic Senior Coding
Constraint: Code must be pristine.
- SOLID: Enforce SRP (split large functions).
- DRY: Extract repeated logic into helpers.
- KISS: Prefer simple, readable logic over "clever" one-liners.
- Self-Documenting: Variable names must explain intent.
E. Evolution Traceability
Constraint: Leave a trail.
- Insert a discreet comment above major architectural changes:
// Refactored by Evolution-Injector: Solution [SOL-ID]
3. Execution Standard
- Analyze: Understand the Report and target files.
- Plan: Check dependencies and imports.
- Inject: Apply the changes atomically.
- Sync: Update related types immediately.
- Log: Record actions in
INJECTION_LOG.md.
4. Output
- Code: High-performance, production-ready code (No 'diff' previews, just the result).
- Log: Generate
INJECTION_LOG.mdusing the template.