Project field explorer
Skill Vit0lze/Project-Evolver-Framework/Skill Files/project-field-explorer
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-field-explorerAssembled 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
Unrestricted deep-dive research into codebase flaws identified in a Global Map. Use when the user wants to investigate 'Breaking Points', plan complex refactors, or prepare a fail-proof execution plan (Connective Handshake) for a future Injector skill.
SKILL.md
2.2 KB, as published. Nobody here has run it
Project Field Explorer
This skill performs a constant, deep-dive research into every structural flaw identifying in GLOBAL_MAP.md. It prepares a fail-proof execution plan for future injection.
1. Trigger & Setup
Trigger: "Use the project-field-explorer skill to investigate the Breaking Points identified in the Global Map."
Data Retrieval:
- Autonomously locate
GLOBAL_MAP.mdin the workspace root orbrain/folder. - Read the Vision section of the map.
- Vision Alignment: Ensure all research prioritizes the stated Project Purpose and Evolution Goal.
2. Deep-Dive Execution Logic
For EACH Breaking Point identified in the Map, perform the following unrestricted analysis:
- Inspect Code: Read the actual source code around the reported
BREAKpoint. - Extract Golden Rules: Identify the hidden business logic that must remain invariant.
"What business value is this messy code actually providing?"
- Blast Radius: Trace references to determine exactly which files will break if this changes.
- Architectural Fit: Consult
references/architectural-solutions.mdto select the best pattern (SOLID, Design Patterns) for the fix.
3. Connective Handshake
For every breaking point, generate a Connective Handshake:
- Solution ID: Assign a unique ID (e.g.,
SOL-AUTH-01). - External Dependencies: Explicitly check and list if new libraries (npm, pip) are needed.
- Target Manifest: List every file path that the future 'Injector' skill will need to modify.
4. Output
Generate a report using assets/templates/FIELD_RESEARCH_REPORT.md for each major issue (or consolidated for related issues).
Constraint Checklist:
- No Limits: Deep dive until clarity is absolute.
- Explicit Deps: Never assume libraries exist. Check them.
- English Only: All reports must be in English.