From idea-forge
HIP-specific extension of tutorial-builder. Adds HIP research phases (4 parallel agents), mirror node integration patterns, hedera-docs submission format, and HIP-specific North Star conventions. Inherits all generic conventions from tutorial-builder.
How this skill is triggered — by the user, by Claude, or both
Slash command
/idea-forge:hip-tutorial-builderThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Foundation exemption:** Inherits the tutorial-builder exemption. Tutorial skills use code-execution quality gates (verify-and-fix loops, milestone acceptance criteria) instead of the document-oriented builder-foundation framework.
Foundation exemption: Inherits the tutorial-builder exemption. Tutorial skills use code-execution quality gates (verify-and-fix loops, milestone acceptance criteria) instead of the document-oriented builder-foundation framework.
This skill extends tutorial-builder. It inherits ALL conventions from skills/builders/tutorial-builder/SKILL.md:
Do NOT duplicate content from tutorial-builder here. This file contains ONLY HIP-specific additions and overrides.
HIP Research (4 parallel) → North Star + Milestones → Milestone 1 → Verify → ... → Docs → hedera-docs submission
The generic tutorial-builder Phase 1 uses general research agents. For HIP tutorials, replace it with four specialized parallel [RESEARCH] agents launched simultaneously in a single message:
Before launching agents: Extract every URL, repo, issue, PR, spec, and reference from the user's initial message. These go into the North Star's Source Materials table.
[RESEARCH] Agent 1 - HIP Specification:
[RESEARCH] Agent 2 - SDK Support:
[RESEARCH] Agent 3 - Mirror Node API:
[RESEARCH] Agent 4 - Existing Docs and Issues:
After all complete, synthesize and present to user: feature capabilities, SDK status, mirror node availability, key risks.
In addition to the standard North Star sections from tutorial-builder, HIP tutorials add:
[RESEARCH] agents simultaneously[SOLIDITY] for writing, then [BLOCKCHAIN_SECURITY] immediately for review (separate agents - adversarial auditing requires a different mindset from authoring)[API_TESTING] on mirror node scripts in parallel with [CODE_REVIEW] on TypeScript scripts[ARCHITECTURE] (HOW_IT_WORKS.md) and [WRITING] (PREREQUISITES.md + GUIDE.md) in parallel[CODE_REVIEW] and [RESEARCH] in parallel for accuracy + fact verificationEvery HIP tutorial must include at least one mirror node query script. Use the mirror node URL from config.ts (single source of truth):
import { getNetworkConfig } from "./utils/config.js";
const { mirrorNodeUrl } = getNetworkConfig();
async function queryFeature(accountId: string): Promise<unknown> {
const url = `${mirrorNodeUrl}/api/v1/accounts/${accountId}/<feature-endpoint>`;
console.log(`Querying: ${url}`);
const res = await fetch(url);
const data = await res.json();
console.log(JSON.stringify(data, null, 2));
return data;
}
In addition to tutorial-builder's 13 writing rules:
https://hashscan.io/<network>/transaction/<txId>For HIP tutorials, BACKGROUND.md must include:
After all milestones complete, create Mintlify MDX tutorial files directly in the hedera-docs repo (not a separate markdown file):
File location: hedera/tutorials/<category>/<tutorial-name>.mdx (e.g., hedera/tutorials/hooks/hello-hooks.mdx)
Structure: Follow existing tutorials (e.g., hedera/tutorials/smart-contracts/hss-x-evm-part-1-*) exactly:
<Note> linking to the public demo repository<Card> linking to Part 2 (if multi-part)<Card> at the bottomMulti-demo tutorials: Split into Part 1 / Part 2 files. Each part is standalone but references the other.
Key rules:
@hiero-ledger/[email protected]), not vendor tarballs/hedera/core-concepts/...), not full docs.hedera.com URLs<Note>, <Warning>, <Info>, <Accordion>, <Card>, <Columns>, <CodeGroup>docs.json navigation to add the new tutorial groupAgent assignments:
[ADVOCACY] writes the tutorial narrative[CODE_REVIEW] verifies every code block matches the demo repo[RESEARCH] verifies all data points (SDK version, fees, endpoints) are currentAfter each HIP tutorial is complete and verified, apply non-obvious learnings back:
What to capture:
Where to apply:
tutorial-builderhip-tutorial-builder (this file)north-star-builderCLAUDE.md Agent Capability RosterWhat NOT to capture: Project-specific logic, one-off debugging solutions, SDK version numbers (go in Key Data Points with dates).
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub kpachhai/idea-forge --plugin idea-forge