exploration-creator
Create exploration content for SHINOBI WAY game with node-based path navigation. Use when user wants to add new regions, locations, room layouts, intel missions, path networks, or exploration mechanics. Guides through the Region→Location→Room hierarchy with intel-gated path choices. (project)
What this skill does
# Exploration System Creator
Create exploration content for SHINOBI WAY: THE INFINITE TOWER following the node-based navigation system with intel-gated path choices.
## Core Hierarchy
```
REGION (e.g., Land of Waves)
├── LOCATION × 10-15 (e.g., The Docks, Fishing Village)
│ ├── ROOM × 10 per location (1→2→4→2→1 branching)
│ │ ├── Rooms 1-9: Random activities (combat, event, merchant, etc.)
│ │ └── Room 10: INTEL MISSION (always elite fight)
│ └── PATHS (connections to other locations)
└── BOSS (final destination)
```
## Key Mechanics
| Mechanic | Description |
|----------|-------------|
| **Forward-Only** | Cannot backtrack to previous locations (roguelike style) |
| **Path Choice** | With intel: choose path. Without: random destination |
| **Intel Mission** | Room 10 elite fight. Win = intel. Skip = random path |
| **Loops** | Special paths back to earlier locations (discovered via intel) |
| **Secrets** | Hidden locations unlocked by intel, items, karma, or story |
## Workflow
### Step 1: Design Region
Define the region's identity:
```typescript
const region: Region = {
id: 'region_id',
name: 'Region Name',
theme: 'Narrative theme description',
description: 'Atmospheric description',
entryPoints: ['location_1', 'location_2'], // 1-2 starting locations
bossLocation: 'boss_location_id',
lootTheme: {
primaryElement: ElementType.WATER,
equipmentFocus: ['speed', 'dexterity'],
goldMultiplier: 0.8
}
};
```
See [region-system.md](references/region-system.md) for complete region structure.
### Step 2: Plan Locations (10-15)
Map locations with danger progression:
| Column | Stage | Danger | Location Count |
|--------|-------|--------|----------------|
| 0 | Entry | 1-2 | 1-2 locations |
| 1 | Early | 3-4 | 2-3 locations |
| 2 | Mid | 4-5 | 3-4 locations |
| 3 | Late | 5-6 | 2-3 locations |
| 4 | Boss | 7 | 1 location |
**Location Types:**
| Type | Combat | Merchant | Rest | Focus |
|------|--------|----------|------|-------|
| `settlement` | Low | Yes | Yes | Story, social |
| `wilderness` | Medium | No | Maybe | Exploration |
| `stronghold` | High | Maybe | No | Heavy combat |
| `landmark` | Medium | Maybe | Maybe | Balanced, story |
| `secret` | Varies | Rare | Rare | Unique rewards |
| `boss` | BOSS | No | No | Final encounter |
See [location-system.md](references/location-system.md) for location data structure and terrain types.
### Step 3: Define Room Activities
Each location has 10 rooms in a 1→2→4→2→1 branching structure. Player visits 5 rooms per location.
**Activity Weights (Rooms 1-9 only):**
| Activity | Weight | Description |
|----------|--------|-------------|
| `combat` | 40% | Fight enemies from location pool |
| `event` | 25% | Atmosphere event with choices |
| `merchant` | 10% | Buy/sell (max 1 per location) |
| `rest` | 8% | Recover HP/Chakra (max 1 per location) |
| `treasure` | 8% | Loot chest |
| `training` | 5% | Permanent stat upgrade |
| `story_event` | 4% | Narrative from story tree |
**Room 10 is ALWAYS an Intel Mission** - elite fight or boss.
See [room-system.md](references/room-system.md) for room layout and connections.
### Step 4: Configure Intel Missions
Every location's Room 10 contains an Intel Mission:
```
Player reaches Room 10 → FIGHT or SKIP
├── FIGHT → Win → Intel + Loot → CHOOSE next path
├── FIGHT → Lose → Game Over
└── SKIP → No rewards → RANDOM next path
```
**Elite scaling by location type:**
| Location Type | Elite Level | Notes |
|---------------|-------------|-------|
| Settlement | 2-3 | Guards, spies |
| Wilderness | 3-5 | Beasts, bandits |
| Stronghold | 5-7 | Commanders |
| Landmark | 4-5 | Guardians |
| Secret | 4-7 | Unique elites |
| Boss | 8-10 | **Cannot skip** |
See [intel-mission-system.md](references/intel-mission-system.md) for intel rewards and boss handling.
### Step 5: Map Path Network
Define connections between locations:
**Path Types:**
| Type | Direction | Discovery | Description |
|------|-----------|-----------|-------------|
| `forward` | → | Always visible | Standard progression |
| `branch` | → | Always visible | Alternative route |
| `loop` | ← | Via intel hint | Return to earlier location |
| `secret` | → | Via intel/item/karma | Hidden location access |
| `boss` | → | Always visible | Final path to boss |
**Navigation Rules:**
1. Forward-only (except loops)
2. Visited locations are closed
3. Intel = player chooses path
4. No intel = random destination
5. Loops are one-time use
6. Boss completes region
See [navigation-system.md](references/navigation-system.md) for path data structures and loop system.
### Step 6: Validate
**Region Checklist:**
- [ ] 10-15 locations total
- [ ] 1-2 entry points (isEntry: true)
- [ ] 1 boss location (isBoss: true)
- [ ] All locations reachable from entry
- [ ] Multiple paths to boss (2-3 minimum)
- [ ] Danger curve: Entry (1-2) → Boss (7)
**Location Checklist:**
- [ ] Unique id and name
- [ ] Valid type and danger level
- [ ] 1-3 forward paths (except boss)
- [ ] Intel mission defined
- [ ] Flags match type
**Room Checklist:**
- [ ] 10 rooms per location
- [ ] Room 10 = intel_mission
- [ ] Max 1 merchant, max 1 rest
- [ ] Connections follow 1→2→4→2→1
See [types.md](references/types.md) for complete TypeScript interfaces.
## Reference Files
- [region-system.md](references/region-system.md) - Region structure and data
- [location-system.md](references/location-system.md) - Location types, terrain, flags
- [room-system.md](references/room-system.md) - 10-room layout and activities
- [intel-mission-system.md](references/intel-mission-system.md) - Elite fights and intel rewards
- [navigation-system.md](references/navigation-system.md) - Paths, loops, secrets
- [types.md](references/types.md) - TypeScript type definitions
- [example-waves.md](references/example-waves.md) - Complete Land of Waves region
## Output Format
Generate TypeScript code for new regions/locations ready to integrate into the game systems.
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.