Menü
Afenda Ask-Docs Quality Standard workflow. Use automatically when authoring, reviewing, or improving content/ask-docs MDX. Composes documentation-audit (code-verified accuracy) and technical-writing (internal-guide prose) with the six-dimension ADQS rubric. Do not invoke sibling skills separately.
| name | adqs |
| description | Afenda Ask-Docs Quality Standard workflow. Use automatically when authoring, reviewing, or improving content/ask-docs MDX. Composes documentation-audit (code-verified accuracy) and technical-writing (internal-guide prose) with the six-dimension ADQS rubric. Do not invoke sibling skills separately. |
| allowed-tools | Read Write Edit Glob Grep Bash |
Target: ≥47.5/50 (95%) per page before merge.
Announce at start: "Applying ADQS workflow to [page path]."
This skill is embedded in .cursor/rules/ask-docs-directory.mdc. Agents editing content/ask-docs/** must follow this workflow without a separate skill invocation.
| Skill | Path | Role in ADQS |
|---|---|---|
documentation-audit | .agents/skills/documentation-audit/SKILL.md | Phase 1 — verify paths, permissions, audit strings against code |
technical-writing | .agents/skills/technical-writing/SKILL.md | Phase 2 — internal-guide prose, headings, operator clarity |
fumadocs-mdx-structure | user skill (Claude) | MDX frontmatter + section skeleton |
fumadocs-component-docs | user skill (Claude) | <Steps>, <Callout>, <Cards>, <Accordions> |
| # | Dimension | 95% requires |
|---|---|---|
| 1 | Frontmatter | title, description (≥8 chars, not duplicate of first paragraph), audience, status, contextual Lucide icon; lastReviewedAt when status: stable |
| 2 | Structure | ## Overview → ## Before you start → workflow → optional ## Troubleshooting → ## Related |
| 3 | Fumadocs components | Non-placeholder <Steps> (≥3 when workflow exists); ≥1 <Callout>; <Cards> in Related; <Tabs> / <Accordions> when multi-path or FAQ |
| 4 | Code-verified accuracy | Paths match App Router; read-only vs mutate correct; step-up and audit match implementation |
| 5 | Link graph | ≥2 /ask-docs/… links; hub + module doc where applicable; passes lint:ask-docs-links |
| 6 | LLM / search | No stub comments; clear ## headings; no "relevant workspace" on audience: employee portal pages |
Gold patterns: content/ask-docs/getting-started/quick-start.mdx, content/ask-docs/hrm/documents.mdx, content/ask-docs/portals/employee.mdx.
Archetypes: workflow · readonly · stepup · hub — scaffold with pnpm gen ask-doc --archetype ….
Before rewriting prose, verify against the codebase:
organization*Path, app/[locale]/o/**, app/[locale]/p/** for the documented surface.requireErpPermission / portal guards for the module; document read vs create vs update.<module>.contract.ts or buildCrudSapAuditAction for canonical action names.Replace with concrete placeholders.Do not ship documentation that contradicts implementation.
Mode: internal-guide for admin/developer pages; route employee portal pages to operator-facing clarity without Workbench jargon.
Apply technical-writing quality checklist — Internal guide checklist:
Section order (mandatory unless archetype exempts):
## Overview
## Before you start
<!-- workflow: <Steps> with ≥3 <Step> when actions exist -->
## Troubleshooting <!-- optional; use <Accordions> for FAQ -->
## Related
<Cards>...</Cards>
pnpm lint:ask-docs-links
pnpm lint:ask-docs-prose
pnpm lint:ask-docs-quality
node scripts/audit-ask-docs-quality.mjs
Tier target: A (≥47.5/50). Locale index pages (index.{locale}.mdx) are partial-exempt.
After edits, state estimated score per dimension and new tier. If still below A, name the smallest missing element (e.g. "add Related Cards with 2 internal links").
status: stable pages/en/ask-docs/…)#features/* imports in docs pages (accuracy via grep only)/o/… or /sign-in in user-facing copy — use /{locale}/o/{orgSlug}/… formYou are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.
Afenda metadata-driven EUI polish workflow. Use automatically when implementing, reviewing, or refining governed renderers (components2/metadata/renderers), surface builders (*-surface-builders.server.ts), Pattern A/B/C ERP pages, or the dev metadata-renderer-gallery. Composes shadcn-metadata, governed-renderer contracts, and Vercel web-design/composition skills. Do not invoke sibling skills separately for the same task.
Write internal technical documentation for engineers and operators: technical specs, architecture docs, ADRs, runbooks, migration plans, and developer-facing implementation guides. Use when the main job is capturing a technical decision, system boundary, operating procedure, or rollout path for builders and maintainers. Triggers on: tech spec, design doc, architecture doc, ADR, runbook, migration guide, implementation guide, rollout doc, operational guide, and internal technical writing. Route API portals to `api-documentation`, end-user help/tutorials to `user-guide-writing`, release notes to `changelog-maintenance`, decks to `presentation-builder`, and GTM messaging to `marketing-automation`.
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".