Skip to content
Skills Library
Programming · Writing

docs

/docs

Use this skill when contributing to InsForge's product documentation in this repository. This is for maintainers editing public docs in `docs/core-concepts`, agent docs in `.agents/docs`, SDK integration guides in `docs/sdks`, and OpenAPI specs in `openapi`.

Repository
InsForge ↗
Licence
Apache-2.0
Last repository change
24.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Use this skill when contributing to InsForge's product documentation in this repository. This is for maintainers editing public docs in `docs/core-concepts`, agent docs in `.agents/docs`, SDK integration guides in `docs/sdks`, and OpenAPI specs in `openapi`.

Original author description

Use this skill when contributing to InsForge's product documentation in this repository. This is for maintainers editing public docs in `docs/core-concepts`, agent docs in `.agents/docs`, SDK integration guides in `docs/sdks`, and OpenAPI specs in `openapi`.

How it works

  1. Scope
  2. Working Rules
  3. Validation
Original SKILL.md headings · 44 lines, 369 words
SKILL.md preview
---
name: docs
description: Use this skill when contributing to InsForge's product documentation in this repository. This is for maintainers editing public docs in `docs/core-concepts`, agent docs in `.agents/docs`, SDK integration guides in `docs/sdks`, and OpenAPI specs in `openapi`.
---

# 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.

3. Prevent documentation drift on every implementation change.
   - Before changing implementation, check the current user-facing docs for that feature.
   - After changing implementation, update the relevant Markdown docs and the relevant OpenAPI YAML files in the same pass.
   - Do not treat OpenAPI and Markdown as separate optional follow-ups when the feature contract or behavior changed.
   - If a change affects agent workflows, update the corresponding file in `.agents/docs/`.
   - If a change affects public product understanding, update the corresponding file in `docs/core-concepts/`, including `architecture.md` when implementation details changed.
   - If a change affects SDK integration guidance, update the corresponding framework guide in `docs/sdks/`.

## Validation

- Re-read every documented command, path, route, and payload for correctness.
- Cross-check OpenAPI YAML and Markdown docs against the implemented behavior before finishing.
- Mention anything you could not verify directly.
Files in this package (2)
  • DOCS_I18N.md 3 KB
  • SKILL.md 3 KB

Versions

RepositoryScoreLicence
This page · InsForge/InsForge90Apache-2.0
tanstack/ai100MIT
mthines/agent-skills100MIT
lilly-logic-labs/lll-skills100MIT
kriscard/kriscard-claude-plugins100MIT
imgly/agent-skills100MIT
kriscard/Skills100MIT
The01Geek/prflow100MIT
grimoire-rs/grimoire100Apache-2.0

Identical content appears in 2 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 53496a2c3e6c (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90insforge-dev
    Use this skill set when contributing to the InsForge monorepo itself. This is for InsForge maintainers and contributors editing the platform, the shared dashboard package, the self-hosting shell, the UI library, shared schemas, tests, or docs.
  • 90ui
    Use this skill when contributing to InsForge's reusable UI package. This is for maintainers editing design-system primitives, exports, styles, and package-level component behavior in the InsForge monorepo.
  • 100insforge-debug
    Rigor Debug / Rigor Audit 技能,面向 Insforge(即时后端/数据库服务)的调试。当用户想排查 Insforge 数据模型、CLI、本地开发或部署问题时使用。
  • 100document
    Technical documentation expert for creating clear, comprehensive documentation including API docs (OpenAPI), ADRs, system architecture docs, developer guides, and runbooks. Use when creating or improving technical documentation.
  • 100md-docs
    Manages project documentation: CLAUDE.md, AGENTS.md, README.md, CONTRIBUTING.md, DOCS.md. Use when asked to update, create, or init these context files. Not for general markdown editing.
  • 95api-documentation-generator
    Generate OpenAPI/Swagger specifications and API documentation from code or design. Use when creating API docs, generating OpenAPI specs, or documenting REST APIs.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.