Add Documentation — NowStack Mobile
SkillDocs & knowledgeAdd or update NowStack Mobile docs in docs/. Use when documenting architecture, release workflows, Convex/web/mobile patterns, setup, APIs, or tooling, or via `/ns docs`.
Use Add Documentation — NowStack Mobile in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Add Documentation — NowStack Mobile and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Add Documentation skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Add Ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
What this skill tells your AI
The instructions your AI receives, as published by melvynx/saveit.now in .agents/skills/ns-add-documentation/SKILL.md and read by Ahel’s review.
-
Scope it before writing. Answer:
- Who reads this — agent, developer, release operator, or support?
- Which surface —
convex/,web-app/,mobile-app/, store release, or sharedsite-config.ts? - What should the reader do differently after reading it?
- Which command or file proves the guidance is still current?
-
Create from the template so frontmatter and structure stay consistent:
.agents/skills/ns-add-documentation/scripts/create-doc.sh <filename> "<title>" "<description>" # e.g. create-doc.sh web-app-routing "Web App Routing" "TanStack Start route conventions"Writes
docs/<filename>.mdfromtemplates/doc-template.md. -
Fill it in — replace every
TODOwith real paths, exact steps, and real verification commands. -
Make it discoverable — link the new doc where a reader would look for it (a sibling doc, or the relevant
.agents/rules/*.md/AGENTS.mdentry). An unlinked doc is a doc nobody finds. -
Verify the commands you wrote actually run (see below), then report the path.
Feature Or Workflow
Purpose
What this solves and when it applies.
Relevant Files
path/to/real/file
Workflow
- Exact step.
Verification
Commands or manual checks that prove it works.
Notes
Caveats, secrets to keep out of git, release constraints.
Deeper conventions: [references/documentation-format.md](references/documentation-format.md).
</structure>
<rules>
- Ground every claim in a real repo file or command — no invented paths, routes, or flags.
- Commands must match `.agents/rules/development-commands.md`.
- Convex docs: state that agents must read `convex/_generated/ai/guidelines.md` before editing `convex/`.
- Cross-surface product/URL/auth/payment facts come from `site-config.ts`.
- Release docs: keep `asc`/`gpc`/screenshot conventions, and keep iOS/Android/store secrets out of git.
- Don't reintroduce the SaaS web-docs tree: no MDX-only components, no `/docs/[slug]`, no NowStack SaaS org routes.
</rules>
<verification>
Run only the checks matching the doc's surface:
```bash
npx convex dev --once # Convex docs compile against the schema
cd web-app && npm run typecheck # web docs
cd web-app && npm run build
cd mobile-app && npx tsc --noEmit # mobile docs
cd mobile-app && npm run lint
cd mobile-app && npm run screenshots:store # store/screenshot docs
<success_criteria>
- The doc lives in
docs/, references only real repo paths, and its commands run. - It's linked from somewhere a reader will actually look.
- No stale public-docs-tree, MDX-only,
/docs/[slug], or NowStack SaaS assumptions remain. </success_criteria>
Signals
- GitHub stars
- 32
- Forks
- 6
- Last commit
- Oct 2026
Advanced
- Item type
- skill
- Key
ns-add-documentation- Source
- github.com/melvynx/saveit.now
More in Docs & knowledge
Skill · mattpocock
More in Docs & knowledgecanvas-design
Skill · anthropics
More in Docs & knowledgedoc-coauthoring
Skill · anthropics
More in Docs & knowledgepopups
Skill · coreyhaines31
More in Docs & knowledgewriting-for-agents
Skill · mattpocock
More in Docs & knowledgespec-driven-development
Skill · addyosmani
More in Docs & knowledge