exploration

Name: exploration
Author: fusengine

21stars3forks

How to install exploration?

fusengine/agents/exploration

$npx -y skills add fusengine/agents --skill exploration

Installs into the current project.

Summary

Codebase exploration techniques for rapid discovery, architecture analysis, pattern detection, and dependency mapping.

Files · 1

View on GitHub

SKILL.md

1	Session: ${CLAUDE_SESSION_ID}
2
3	# Exploration Skill
4
5	## Exploration Protocol
6
7	Run these 5 phases in order — full commands in `references/exploration-protocol.md`:
8
9	1. Initial Reconnaissance — list root files, find config files, check common entry points
10	2. Structure Mapping — tree view (excluding noise dirs), identify main directories
11	3. Entry Points Detection — grep for `main`/`index`/server bootstrap per language
12	4. Dependency Analysis — read `package.json`/`pyproject.toml`/`go.mod`/`Cargo.toml`/`composer.json`
13	5. Pattern Detection — check for MVC, Clean/Hexagonal, feature-based, Next.js App Router directories
14
15	---
16
17	## Architecture Pattern Detection
18
19	### Pattern Indicators
20
21	\| Pattern \| Key Directories \| Indicators \|
22	\|---------\|-----------------\|------------\|
23	\| MVC \| `controllers/`, `models/`, `views/` \| Rails, Laravel, Express \|
24	\| Clean Architecture \| `domain/`, `application/`, `infrastructure/` \| DDD, Use cases \|
25	\| Hexagonal \| `adapters/`, `ports/`, `core/` \| Ports & adapters \|
26	\| Feature-based \| `features/[name]/` \| All layers per feature \|
27	\| Layered \| `presentation/`, `business/`, `data/` \| Traditional 3-tier \|
28	\| Monolith \| Single `src/` \| Mixed concerns \|
29	\| Microservices \| Multiple `services/` \| Separate repos/folders \|
30	\| Next.js App Router \| `app/`, `components/`, `lib/` \| Server/Client components \|
31	\| Modular Monolith \| `modules/[name]/` \| Bounded contexts \|
32
33	---
34
35	## Forbidden Behaviors
36
37	- ❌ Make assumptions without code evidence
38	- ❌ Ignore configuration files
39	- ❌ Overlook test directories
40	- ❌ Skip dependency analysis
41	- ❌ Miss entry points
42	- ❌ Assume architecture without verification
43
44	## Behavioral Traits
45
46	- Systematic and methodical
47	- Pattern-focused detection
48	- Context-aware analysis
49	- Comprehensive yet concise
50	- Evidence-based insights
51	- Quick reconnaissance before deep dive
52
53	---
54
55	## Detailed References (Load on Demand)
56
57	- `references/exploration-protocol.md` — Load when running the 5-phase protocol (exact shell commands per phase)
58	- `references/tech-stack-detection.md` — Load when identifying framework/ORM/tooling per language (JS/TS, Python, Go, PHP, Rust)
59	- `references/code-organization-checks.md` — Load when auditing interface separation, business-logic location, or state management
60	- `references/response-format.md` — Load when writing the final exploration report
61	- `references/quick-analysis-commands.md` — Load for one-liner full-stack assessment, file counts, or large-file detection

People who liked this also viewed

6 picks

Type

agent-browserBrowser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web aSkillsJul 2026571k39k
browser-act--- name: browser-act description: "Browser automation CLI for AI agents. NEVER run browser-act commands directly via Bash — always invoke this skill first. Use browser-act when a user mentions it bSkillsJul 2026107k4.6k
playwright-cliAutomate browser interactions, test web pages and work with Playwright tests.SkillsJul 202695k12k
accessibilityAudit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make SkillsJun 202638k2.5k
anti-detect-browserLaunch and manage anti-detect browsers with unique real-device fingerprints for multi-account operations, web scraping, ad verification, and AI agent automation. Use when the user needs to run multiplSkillsMar 202630k3
web-access所有联网操作必须通过此 skill 处理，包括：搜索、网页抓取、登录后操作、网络交互等。触发场景：用户要求搜索信息、查看网页内容、访问需要登录的网站、操作网页界面、抓取社交媒体内容（小红书、微博、推特等）、读取动态渲染页面、以及任何需要真实浏览器环境的网络任务。SkillsMay 202615k8.4k

exploration

21stars3forks

View on GitHub

How to install exploration?

fusengine/agents/exploration

$npx -y skills add fusengine/agents --skill exploration

Installs into the current project.

Summary

Codebase exploration techniques for rapid discovery, architecture analysis, pattern detection, and dependency mapping.

Files · 1

View on GitHub

SKILL.md

1	Session: ${CLAUDE_SESSION_ID}
2
3	# Exploration Skill
4
5	## Exploration Protocol
6
7	Run these 5 phases in order — full commands in `references/exploration-protocol.md`:
8
9	1. Initial Reconnaissance — list root files, find config files, check common entry points
10	2. Structure Mapping — tree view (excluding noise dirs), identify main directories
11	3. Entry Points Detection — grep for `main`/`index`/server bootstrap per language
12	4. Dependency Analysis — read `package.json`/`pyproject.toml`/`go.mod`/`Cargo.toml`/`composer.json`
13	5. Pattern Detection — check for MVC, Clean/Hexagonal, feature-based, Next.js App Router directories
14
15	---
16
17	## Architecture Pattern Detection
18
19	### Pattern Indicators
20
21	\| Pattern \| Key Directories \| Indicators \|
22	\|---------\|-----------------\|------------\|
23	\| MVC \| `controllers/`, `models/`, `views/` \| Rails, Laravel, Express \|
24	\| Clean Architecture \| `domain/`, `application/`, `infrastructure/` \| DDD, Use cases \|
25	\| Hexagonal \| `adapters/`, `ports/`, `core/` \| Ports & adapters \|
26	\| Feature-based \| `features/[name]/` \| All layers per feature \|
27	\| Layered \| `presentation/`, `business/`, `data/` \| Traditional 3-tier \|
28	\| Monolith \| Single `src/` \| Mixed concerns \|
29	\| Microservices \| Multiple `services/` \| Separate repos/folders \|
30	\| Next.js App Router \| `app/`, `components/`, `lib/` \| Server/Client components \|
31	\| Modular Monolith \| `modules/[name]/` \| Bounded contexts \|
32
33	---
34
35	## Forbidden Behaviors
36
37	- ❌ Make assumptions without code evidence
38	- ❌ Ignore configuration files
39	- ❌ Overlook test directories
40	- ❌ Skip dependency analysis
41	- ❌ Miss entry points
42	- ❌ Assume architecture without verification
43
44	## Behavioral Traits
45
46	- Systematic and methodical
47	- Pattern-focused detection
48	- Context-aware analysis
49	- Comprehensive yet concise
50	- Evidence-based insights
51	- Quick reconnaissance before deep dive
52
53	---
54
55	## Detailed References (Load on Demand)
56
57	- `references/exploration-protocol.md` — Load when running the 5-phase protocol (exact shell commands per phase)
58	- `references/tech-stack-detection.md` — Load when identifying framework/ORM/tooling per language (JS/TS, Python, Go, PHP, Rust)
59	- `references/code-organization-checks.md` — Load when auditing interface separation, business-logic location, or state management
60	- `references/response-format.md` — Load when writing the final exploration report
61	- `references/quick-analysis-commands.md` — Load for one-liner full-stack assessment, file counts, or large-file detection

People who liked this also viewed

6 picks

Type