daggerheart-core-rules
Comprehensive guide to the Daggerheart Tabletop Roleplaying Game (TTRPG). Use this skill when users ask questions about Daggerheart rules, character creation, classes, gameplay mechanics, GM guidance, adversaries, or lore.
Best use case
daggerheart-core-rules is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Comprehensive guide to the Daggerheart Tabletop Roleplaying Game (TTRPG). Use this skill when users ask questions about Daggerheart rules, character creation, classes, gameplay mechanics, GM guidance, adversaries, or lore.
Teams using daggerheart-core-rules should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/daggerheart-core-rules/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How daggerheart-core-rules Compares
| Feature / Agent | daggerheart-core-rules | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Comprehensive guide to the Daggerheart Tabletop Roleplaying Game (TTRPG). Use this skill when users ask questions about Daggerheart rules, character creation, classes, gameplay mechanics, GM guidance, adversaries, or lore.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Daggerheart Core Rules Skill
This skill allows you to answer questions about the Daggerheart RPG by referencing the Core Rulebook.
## Rulebook Structure
The rulebook is organized into several main markdown files in `references/`.
### Directory Map
- **Introduction & Principles** (`references/01_introduction_and_principles.md`)
- **Character Creation** (`references/02_character_creation.md`)
- **Core Mechanics** (`references/03_core_mechanics.md`)
- **Equipment** (`references/04_equipment.md`)
- **Running the Game (GM Guide)** (`references/05_running_the_game_gm_guide.md`)
- **Adversaries & Environments** (`references/06_adversaries_and_environments.md`)
- **Campaign Frames** (`references/07_campaign_frames.md`)
- **Appendix & Reference** (`references/08_appendix_and_reference.md`)
## Advanced Workflows
For complex GM scenarios, consult the specialized guides in `references/workflows/`:
1. **Character Analysis** (`character_logic.md`): Use for questions about specific PC/NPC builds, class feature interactions, or conflicting rules.
2. **Worldbuilding & Narrative** (`worldbuilding.md`): Use for creating custom locations, lore questions, or describing scenes with Daggerheart flavor.
3. **Adversary Tactics** (`adversary_tactics.md`): Use for questions about monster behavior, combat balance, or running encounters.
4. **GM Improvisation** (`gm_improv.md`): Use when the GM needs help reacting to unexpected player choices, "failing forward," or redirecting the plot.
5. **Combat Orchestration** (`combat_orchestration.md`): Use for managing the Action Tracker, range bands, and the spotlight during combat.
6. **Leveling & Multiclassing** (`leveling_multiclassing.md`): Use for character advancement, trait upgrades, and multiclassing rules.
7. **Session Zero & Planning** (`session_zero_planning.md`): Use for starting campaigns, setting safety tools, and collaborative worldbuilding.
## How to Use
1. **Identify the Intent:**
* **Simple Rule Lookup:** Proceed to step 2 (Search References).
* **Complex Scenario:** Match the request to one of the "Advanced Workflows" above and follow its steps.
2. **Search References:**
- Use `search_file_content` to find specific keywords across the relevant reference files (e.g., search "Stress" in `references/03_core_mechanics.md`).
3. **Read Context:** Read the relevant files to understand the rules. Information often spans multiple pages.
4. **Cite Page Numbers:** Always include the page number in your response. Page numbers can be identified by the `<!-- PAGE_START: XXX -->` markers within the main reference files. Format citations as `(p. XXX)`.
## Style Guide
- **Citations:** Every rule or piece of lore you quote should be followed by a page citation, e.g., "Duality Dice consist of a Hope die and a Fear die (p. 090)."
- **Terminology:** Use exact game terms (e.g., "Hope Die", "Fear Die", "Action Tracker", "Experiences").
- **Mechanics:** When explaining mechanics, be precise about dice rolls, modifiers, and resource costs.
- **Lore:** Distinguish between "flavor text" and actual mechanics.Related Skills
sync-rules
Synchronize shared rules into agent context files and headers.
publishing-rules
Rules for publishing Chrome extensions to the Chrome Web Store, ensuring proper submission guidelines are followed.
portable-skills-and-rules
Defines SKILL.md structure, valid frontmatter fields, and cross-tool setup for Claude Code, Cursor, OpenCode, and Cline. ALWAYS read before creating or editing any SKILL.md file. This skill should be used when "writing a skill", "creating a skill", "editing a skill", "skill frontmatter", "SKILL.md format", "AGENTS.md", "CLAUDE.md", or setting up skills across multiple AI tools.
install-rules
Install rules from this project or a specified Git repo into Cursor or Trae IDE. Use when the user wants to add project/global rules to their editor from ai-cortex rules/ or another repository.
HexCore Binary Analysis
Skill para analise de binarios com ferramentas HexCore integradas ao editor
faf-score
Calculate AI-readiness score (0-100%) for any project with project.faf file. Shows Podium tier (Trophy/Gold/Silver/Bronze), identifies strengths and gaps, provides improvement roadmap. Use when user asks "what's my score", "how AI-ready is this", "check my FAF quality", or wants to measure project context completeness.
customer-health-scorecard
Create or update a customer health scorecard
ckeditor-rules
Defines CKEditor is being used for text editing
build-notes-file-rules
Enforces rules for creating and managing build notes files within the /ProjectDocs/Build_Notes/ directory, including naming conventions, content structure, and update frequency.
ai-rules-adapter-builder
Add rules or skills adapters for a new AI tool and wire config, CLI, completion, and tests.
tauri-security-rules
Security-related rules for Tauri application development.
security-core
Comprehensive application security expertise covering authentication, authorization, OWASP Top 10, and security best practices. Use when (1) Implementing authentication (JWT, OAuth2, sessions, OAuth for CLI/TUI/desktop apps), (2) Adding authorization (RBAC, ABAC, RLS with Supabase/PostgreSQL), (3) Security auditing code or infrastructure, (4) Setting up security infrastructure (headers, CORS, CSP, rate limiting), (5) Managing secrets and credentials, (6) Preventing OWASP Top 10 vulnerabilities (injection, XSS, CSRF, etc.), (7) Reviewing code for security issues, (8) Configuring secure web applications in TypeScript, Python, or Rust. Automatically triggered when working with authentication/authorization systems, security reviews, or addressing security vulnerabilities.