discover

النجوم١٠

التفرعات٢

آخر تحديث٢٨ مايو ٢٠٢٦ في ٠٢:٠٦

Scans the existing codebase to initialize or update the architecture.yml hypergraph.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

المصدر

tjmustard

tjmustard/OIN-SMILES

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name	discover
description	Scans the existing codebase to initialize or update the architecture.yml hypergraph.
trigger	/hyper-discover

ROLE: The Discovery Agent

Your objective is to perform a recursive scan of the existing repository to map its topological structure into the architecture.yml hypergraph schema.

CRITICAL RULES

Top-Down Discovery: Start with the directory structure to identify "Module" nodes. Then drill into files to identify "Atomic" nodes (functions, classes, components).
Dependency Mapping: Pay strict attention to imports and exports. These define the depends_on edges in the YAML.
Semantic Analysis: Do not just list files. Read the code to provide a concise description of the node's semantic purpose.

EXECUTION PHASES

[PHASE 1: Directory Mapping]

Identify the major folders and map them to "Module" dimension nodes in the hypergraph.

[PHASE 2: Atomic Extraction]

For each major file, identify the core functions or classes. Map these to "Atomic" dimension nodes.
Link them to their parent Module via the implements edge.

[PHASE 3: Edge Detection]

Trace the data flow. If File A imports File B, File B is a dependency. Map this to the depends_on edge.

OUTPUT

Update or create spec/compiled/architecture.yml. Set all newly discovered nodes to status: clean. Output a summary of the system's topological density (number of modules vs. atomic nodes).

Final Action:

If creating the file from scratch, save the compiled YAML to spec/compiled/architecture.yml.
If appending/modifying an existing graph, you MUST execute python .agents/scripts/hypergraph_updater.py spec/compiled/architecture.yml [modified_node_ids] via your terminal tool to properly propagate the Blast Radius.

المزيد من هذا المستودع

نفس المستودع

hyper-document

tjmustard/OIN-SMILES

Updates all project documentation after code or skill changes. Always reads actual implementation before writing. Covers README, CHANGELOG, docs/, AGENTS.md, memory files, and skills-info.md. Use after completing any feature, fix, refactor, or skill update.

2026-07-2710

handoff

tjmustard/OIN-SMILES

Compacts the current conversation into a handoff document so a fresh agent can continue the work. Saves to the OS temp directory, not the workspace. Pass an optional argument describing what the next session will focus on.

2026-07-2510

process-document

tjmustard/OIN-SMILES

Documents the process, methodology, and decisions of the current session as a reproducible narrative. Saves to spec/process/ in the workspace so the journey can be understood and recreated by others.

2026-07-2510

hyper-init

tjmustard/OIN-SMILES

Scaffolds a new project by conducting an interview to collect metadata and generating standard repository documentation files from the framework templates. Use when setting up a new repository.

2026-07-0310

hyper-tutorial-audit

tjmustard/OIN-SMILES

Run this after /hyper-tutorial-run to turn tutorial failures into a structured, constraint-aware goal prompt. Interviews the user about their goal and what may/may not be changed, then generates a paste-ready prompt for a new Claude Code fix session. Does NOT re-run tutorial commands.

2026-07-0310

tutorial-generator

tjmustard/OIN-SMILES

Generates a markdown tutorial from an integration test or user-provided files through iterative LLM + human collaboration. Tutorials are saved to tutorials/<name>/ with organized supporting files.

2026-07-0310

name	discover
description	Scans the existing codebase to initialize or update the architecture.yml hypergraph.
trigger	/hyper-discover

ROLE: The Discovery Agent

Your objective is to perform a recursive scan of the existing repository to map its topological structure into the architecture.yml hypergraph schema.

CRITICAL RULES

Top-Down Discovery: Start with the directory structure to identify "Module" nodes. Then drill into files to identify "Atomic" nodes (functions, classes, components).
Dependency Mapping: Pay strict attention to imports and exports. These define the depends_on edges in the YAML.
Semantic Analysis: Do not just list files. Read the code to provide a concise description of the node's semantic purpose.

EXECUTION PHASES

[PHASE 1: Directory Mapping]

Identify the major folders and map them to "Module" dimension nodes in the hypergraph.

[PHASE 2: Atomic Extraction]

For each major file, identify the core functions or classes. Map these to "Atomic" dimension nodes.
Link them to their parent Module via the implements edge.

[PHASE 3: Edge Detection]

Trace the data flow. If File A imports File B, File B is a dependency. Map this to the depends_on edge.

OUTPUT

Update or create spec/compiled/architecture.yml. Set all newly discovered nodes to status: clean. Output a summary of the system's topological density (number of modules vs. atomic nodes).

Final Action:

If creating the file from scratch, save the compiled YAML to spec/compiled/architecture.yml.
If appending/modifying an existing graph, you MUST execute python .agents/scripts/hypergraph_updater.py spec/compiled/architecture.yml [modified_node_ids] via your terminal tool to properly propagate the Blast Radius.