nekans-skills

Orchestrates NetEase Mod development across three resumable sessions with staged planning, testing, and review.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Coral5644/NekansModPack --skill nekans-skills-coral5644
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nekans-skills
Source: https://github.com/Coral5644/NekansModPack/tree/main/.cursor/skills/nekans-skills
Command: npx skills add https://github.com/Coral5644/NekansModPack --skill nekans-skills-coral5644

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long NetEase Mod development tasks often exceed a single AI conversation, causing context compression and lost progress mid-execution. This Skill splits the full workflow into three stable sessions with state files and handoff prompts so work can resume reliably. ## Core Features & Use Cases - Three-Session Workflow: Session 1 covers workspace selection, brainstorming, and planning; Session 2 handles execution, batch code review, and direct testing via mcdev-tools; Session 3 performs final review, regression verification, and cleanup. - State Files & Handoff Prompts: Writes session state to Docs/sessions/<business>/ and generates copy-paste relay prompts so the next session restores full context. - Workspace Modes: Supports main-workspace or feature-workspace development, with direct testing of feature workspaces through mcdev-tools before any merge. - Use Case: When building a large new NetEase Mod feature, use this Skill to plan in one conversation, execute and test in a second, and finalize review and cleanup in a third without losing context. ## Quick Start Start a new NetEase Mod feature task and ask the AI to follow the nekans-skills workflow beginning with the workspace location question.

Frequently Asked Questions about nekans-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split a long AI coding task across multiple sessions?▼

Split the work into three sessions: planning, execution with testing, and final review with cleanup. At each session boundary, write a state file under Docs/sessions/ and generate a copy-paste handoff prompt so the next session restores full context.

How to test a NetEase Mod feature workspace without merging?▼

Point the included_mod_dirs field in .mcdev.json at the feature workspace, restart the game via mcdk, and test directly. Fix failures in the feature workspace and retest; only merge to the main workspace after tests pass.

What is the workflow for NetEase Mod feature development?▼

The workflow has six stages: workspace selection, requirements brainstorming, implementation planning, execution with batch code review, final review, and cleanup. Stages are distributed across three sessions to avoid context compression.

Should I develop in the main workspace or a feature workspace?▼

The workflow requires the user to decide at the start of every session; the AI never chooses. Feature workspaces isolate changes and support direct testing via mcdev-tools, while the main workspace allows direct modification and testing in place.

When should final code review happen in this workflow?▼

Final review happens only in the third session, after execution and integration testing pass in the second session. If review fixes change code, a minimal regression test is run before cleanup.