InsForge Dev Docs

Use this skill for docs/core-concepts/, .agents/docs/, docs/sdks/, and openapi/ in the InsForge repository.

The documentation in this repo is primarily product documentation for InsForge users and agents integrating with InsForge. This skill is for InsForge engineers maintaining that public documentation surface.

Scope

• docs/core-concepts/**
• .agents/docs/**
• docs/sdks/**
• openapi/**

Working Rules

1. Put each document in the correct documentation surface.

   • Human-friendly docs published on the public doc site belong in docs/core-concepts/ and related public doc folders.
   • For implementation-heavy public docs, prefer an architecture.md file inside the relevant docs/core-concepts/<domain>/ folder.
   • Agent-only instructions belong in .agents/docs/.
   • SDK integration guides for each framework belong in docs/sdks/.
   • OpenAPI contract changes belong in the matching files under openapi/.

2. Match the writing style to the audience.

   • Public docs should be human-friendly and explain the implementation clearly.
   • Keep public docs human-sounding: avoid AI-writing tells such as em dashes, rule-of-three lists, "not just X but Y" parallelism, inflated significance, vague attribution, and AI vocabulary (delve, leverage, underscore, seamless, robust). See the doc-author skill's INSFORGE.md overlay, "Sound human, not AI-generated".
   • architecture.md pages in docs/core-concepts/ should explain how the feature works in detail.
   • Agent docs in .agents/docs/ should be instruction-first and execution-oriented.
   • Agent docs should avoid explanatory filler and focus on the exact steps an agent should follow to complete the work.