quest-index

Organize and document the public API of the quest module.

1|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/diadia0000/ForWanna --skill quest-index
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quest-index
Source: https://github.com/diadia0000/ForWanna/tree/main/.claude/skills/quest/index
Command: npx skills add https://github.com/diadia0000/ForWanna --skill quest-index

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a clear, structured guide for developers integrating the quest module, ensuring they understand which symbols are exposed and which are omitted for a clean API surface.

Core Features & Use Cases

  • API Surface Management: Offers a straightforward view of the public interface for the quest module, including re-exported types and functions.
  • Development Workflow: Facilitates the integration of the quest module by clearly defining the entry points and dependencies.
  • Use Case: When a developer is building a game using the quest module, they can refer to this Skill to quickly understand what is available and how to properly import and use it.

Quick Start

Run the quest skill to review the public API and available symbols for the quest module.

Frequently Asked Questions about quest-index

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

FAQPage Schema
What is the quest module's public API surface and what symbols are re-exported?

The quest module API surface is a structured list of re-exported types and functions. It exposes available entry points and dependencies while omitting internal symbols to maintain a clean interface for game development integration.

How do I integrate the quest module into my game development project?

To integrate the quest module, run the quest skill to review its public API and available symbols. This defines the entry points and dependencies needed to properly import and use the module in your project.

When do I need to check the quest module's re-exported types and functions?

You need to check the quest module's re-exported types and functions when you are building a game and require a clear understanding of which symbols are exposed for import and which are omitted from the public interface.

Can I use the quest module API documentation to manage symbol imports for my development workflow?

Yes, you can use the quest module API documentation to manage symbol imports. It facilitates your development workflow by clearly defining entry points and dependencies, ensuring you only import exposed symbols.

Does the quest module API guide include internal symbols or only public entry points?

The quest module API guide includes only public entry points. It omits internal symbols to ensure a clean API surface, providing a straightforward view of re-exported types and functions for developers.