wahidyankf

Complete authoring methodology for Annotated-concept tutorials on ayokoding-web — mode selection (standard vs. no-code sub-mode), worked-example/scenario requirements, diagram requirements, the content-creation workflow, and quality standards. Backs the apps-ayokoding-www-annotated-concept-maker agent.

Validates software engineering documentation separation between OSE Platform style guides (docs/explanation/) and AyoKoding educational content (apps/ayokoding-www/). Ensures no duplication, proper prerequisite statements, and style guide focus on repository-specific conventions only.

Common software development workflow patterns shared across all language developer agents

Complete methodology for spec-aware, contract-aware session-based exploratory testing of a live REST or GraphQL API — inputs, relationships, non-destructive constraint, charter/tour/SFDIPOT methodology, test dimensions, mandatory systematic sweeps, driving the API, contract-and-specs ground truth, defect anatomy, and output modes. Backs the api-exploratory-tester agent.

Spec-aware session-based exploratory testing methodology for web-exploratory-tester — charter framing, testing tours, SFDIPOT/CRUSSPIC STMPL coverage models, the test dimensions checklist, three mandatory systematic sweeps, specs-as-ground-truth comparison and spec-gap detection, defect anatomy, and the three output modes (plan/delivery/local-tmp).

Guide for creating in-the-field production implementation guides - production-ready code with 20-40 guides following standard library first principle, framework integration, and enterprise patterns. Essential for creating production tutorials for programming languages on educational platforms

Shared repository vocabulary — what "repo rules", the four content trees, delivery units, and governance surfaces actually cover. Auto-loads when a task involves repository rules, governance scope, plans, delivery units, agent or skill boundaries, or any judgement about whether a rule reaches a given file.

Guide for creating content on ayokoding-web, a Next.js 16 fullstack content platform (ayokoding-web). Covers bilingual content strategy (default English), tRPC API, content workflow, and ayokoding-web specific patterns. Essential for content creation tasks on ayokoding-web

Universal classification system for checker and fixer agents using orthogonal criticality (CRITICAL/HIGH/MEDIUM/LOW importance) and confidence (HIGH/MEDIUM/FALSE_POSITIVE certainty) dimensions. Covers priority matrix (P0-P4), execution order, dual-label pattern for verification status, standardized report format, and domain-specific examples. Essential for implementing checker/fixer agents and processing audit reports

Playwright E2E testing standards from authoritative docs/explanation/software-engineering/automation-testing/tools/playwright/ documentation

Guide for developing organiclever-www, the OrganicLever life journal at www.organiclever.com. Covers feature-context architecture, PGlite local-first storage, Effect TS, XState, Next.js 16 App Router, and Vercel deployment. Essential for development tasks on organiclever-www.

Format standards for Annotated-concept tutorials (concept-centric worked examples, standard and no-code sub-mode) shared by the ayokoding-www maker/checker/fixer family

Six-layer governance hierarchy (Vision → Principles → Conventions → Development → Agents → Workflows). Use when understanding repository structure, tracing rules to foundational values, explaining architectural decisions, or navigating layer relationships.

Complete methodology for re-validating and applying docs-checker factual-accuracy findings without web access — the trust model, domain-specific confidence examples, per-finding-type re-validation guidance, fix application patterns, the fix report format, and convergence safeguards. Backs the docs-fixer agent.

Domain-specific methodology for docs-tutorial-fixer — re-validating docs-tutorial-checker findings on pedagogical structure, then applying fixes only for objective issues (missing sections, LaTeX delimiters, naming, time estimates, frontmatter) while flagging subjective narrative/style findings for manual review. Use when applying validated fixes from a tutorial audit report.

Universal markdown content quality standards for active voice, heading hierarchy, accessibility compliance (alt text, WCAG AA contrast, screen reader support), and professional formatting. Essential for all markdown content creation across docs/, web sites, plans/, and repository files. Auto-loads when creating or editing markdown content.

Complete methodology for safely renaming, moving, and deleting files/directories in docs/ — file naming review, the four-phase systematic process, deletion safety, link updates, git operations, index updates, validation checklists, safety guidelines, edge cases, and integration with other agents. Backs the docs-file-manager agent.

Guide for writing Gherkin acceptance criteria using Given-When-Then syntax for testable requirements. Covers scenario structure, background blocks, scenario outlines with examples tables, common patterns for authentication/CRUD/validation/error handling, and best practices for clear testable specifications. Essential for writing user stories and plan acceptance criteria

The shared execution protocol inherited verbatim from the retired pr-review-maker monolith by all nine discipline-scoped pr-review-*-maker specialists (architecture, docs, governance, instruction, integrity, logic, performance, security, types) - context consumption, finding requirements hard rules, scope guard, untrusted-input handling, findings handoff (no direct posting), cross-cycle behaviour, and external fact verification. Use when reviewing a PR as one of the nine discipline specialists.

Shared deployment procedure for the `*-deployer` agent family — force-pushing an environment branch that Vercel (or a GitHub Actions workflow) builds from. Covers three patterns (direct force-push, scheduled staging workflow, scheduled test-only workflow) plus the shared Vercel MCP post-deploy verification protocol. Use when authoring or invoking any `apps-*-deployer` agent.

Cross-vendor parity invariants, lifecycle delegation, and seven external-drift dimensions shared by the harness compatibility checker and fixer.

How pr-review-scout-maker selects one pass's risk tier and specialist set, assembles shared context, and reads authenticated prior state.

Guide for creating content on ose-web Next.js 16 content platform. Covers English-only landing page structure, update posts with date-prefixed filenames, markdown frontmatter (title, date, tags, summary, showtoc), simple flat organization, and ose-web specific conventions. Essential for ose-web content creation tasks

PDF-to-Markdown conversion fidelity — the crane CLI, criticality levels, and workflow steps shared by the pdf-to-md maker/checker/fixer family

Diátaxis documentation framework for organizing content into four categories - tutorials (learning-oriented), how-to guides (problem-solving), reference (technical specifications), and explanation (conceptual understanding). Essential for creating and organizing documentation in docs/ directory.

The docs-tutorial-maker agent's structural methodology - the seven tutorial types and coverage levels, the tutorial-specific diagram orientation override (LR default, not the general TD default), the seven-section tutorial template (frontmatter through troubleshooting), and the create/update workflows with tutorial-specific quality requirements. Use when creating or updating tutorial documentation under docs/tutorials/.

Universal methodology for verifying factual correctness in documentation using WebSearch and WebFetch tools. Covers command syntax verification, version checking, code example validation, API correctness, confidence classification system ([Verified], [Error], [Outdated], [Unverified]), source prioritization, and update frequency rules. Essential for maintaining factual accuracy in technical documentation and educational content

How pr-review-synthesis-maker deduplicates, re-categorizes, reasonableness-filters, and tool-verifies the nine discipline specialists' raw findings, then posts exactly one consolidated GitHub review. Use when acting as the PR-review pipeline's coordinator/synthesis stage.

Spec-blind heuristic usability evaluation methodology for web-usability-tester — Nielsen's 10 heuristics, cognitive walkthrough, first-click/information-scent analysis, the usability dimensions checklist, four mandatory systematic probes, URL naturalness, responsive usability, finding anatomy, and the three output modes (plan/delivery/local-tmp).

WCAG-compliant Mermaid diagrams using verified accessible color palette. Use when creating diagrams, flowcharts, or any color-dependent visualizations requiring accessibility compliance for color blindness.

Three-stage content quality workflow pattern (Maker creates, Checker validates, Fixer remediates) with detailed execution workflows. Use when working with content quality workflows, validation processes, audit reports, or implementing maker/checker/fixer agent roles.

Guide for creating by-example tutorials - code-first learning path with 75-85 heavily annotated examples achieving 95% language coverage. Covers five-part example structure, annotation density standards (1.0-2.25 comments per code line PER EXAMPLE), self-containment rules, and multiple code blocks for comparisons. Essential for creating by-example tutorials for programming languages on educational platforms

Guidelines for generating validation/audit reports with UUID chains, progressive writing, and UTC+7 timestamps

Post-execution verification methodology for plan-execution-checker — confirms completed plan implementation actually did what the plan said, as the temporal sibling of plan-validating-quality's pre-execution rules (same rule domains — operational readiness, manual assertions, worktree usage, anti-hallucination, knowledge capture, delivery mode — checked against the post-execution repo state instead of the authored plan text).

Invocable entry point for the plan-ideas-grooming workflow — sweeps one or more repos' plans/ideas/ folders and converges them into a deduplicated, Eisenhower-quadrant-organized, correctly-resident set of two-pagers. Carries the ten-step procedure, the three residency rules (secrets-bearing, single-repo-only, generalizable), the two classification rubrics (urgency, importance), the fail-safe-toward-duplication relocation sequence, and the six-clause termination audit. Use when a repo's flat idea count exceeds 60, when 90 days have elapsed since the last recorded run, or when a maintainer asks for idea grooming across repos.

How pr-review-fixer enumerates unresolved GitHub PR review threads, triages each into fix/reject/defer/clarify, applies the outcome, and resolves only what was genuinely addressed. Use when resolving threads posted by pr-review-synthesis-maker's consolidated review.

Validation methodology for specs/ folders — nine categories covering README/feature-file structural completeness, Gherkin format compliance, cross-folder consistency, C4 diagrams, cross-references, spec-to-implementation alignment, tree-shape compliance, and BDD/contracts adoption gaps. Used by specs-checker and specs-fixer.

UI development skill covering design token usage, shadcn/ui + Radix composition patterns, accessibility requirements, anti-patterns catalog, and brand context for OrganicLever and OSE Platform. Auto-loads when working on TSX components, CSS, or UI design tasks.

TypeScript coding standards from authoritative docs/explanation/software-engineering/programming-languages/typescript/ documentation

Project planning standards for authorized plans/ artifacts, including lifecycle naming, fixed mature core, bootcamp-graduate readability, alternatives and prior art, Gherkin criteria, granular delivery checklists, and evidence-first grilling.

README quality standards for engaging, accessible, scannable content including problem-solution hooks, plain language (no unexplained jargon), acronym context, paragraph limits (≤5 lines), benefits-focused language, visual hierarchy, and progressive disclosure. Essential for creating effective README files that welcome and guide users.

The task-list obligation every agent carries — open the harness's native task list before any task, conversational ones included, and keep it in sync with actual progress. Auto-loads whenever work is about to begin.

Complete validation methodology for repository-wide governance consistency — file naming/linking/emoji, agent-Skill and Skill-to-Skill duplication/consolidation, governance word budgets, rules-governance contradictions/traceability/licensing/dependency-bump-policy, and software-engineering documentation quality. Used by rules-checker.

Complete methodology for design-aware live-site evaluation — inputs, the swe-ui-checker boundary, non-destructive constraint, design-fidelity + design-practice evaluation, the five ground-truth sources, dimensions checklist, mandatory systematic checks, browser driving, finding anatomy, and output modes. Backs the web-design-tester agent.

Interview the user relentlessly about a plan or design, presenting choices one at a time until shared understanding is reached. Resolves every branch of the decision tree. Use when the user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

CI/CD standards knowledge for project-role targets, static BDD coverage, runtime boundaries, hooks, and scheduled tests

Mechanics for specs-maker — the four surface-profile directory trees, README/feature-file/C4-diagram content generation, and the PM-readability/placement/structure conventions every scaffolded file follows.

Java coding standards from authoritative docs/explanation/software-engineering/programming-languages/java/ documentation

Rust coding standards from authoritative docs/explanation/software-engineering/programming-languages/rust/ documentation

Link validation methodology for markdown links including format requirements, path validation, broken link detection, external link verification, and checker implementation patterns

How readme-fixer re-validates readme-checker findings, assesses HIGH/MEDIUM/FALSE_POSITIVE confidence for README-specific issues, and applies fixes only for objective/verifiable problems. Use when re-validating or applying README quality fixes.

Run the rules-propagation workflow whenever a repository rule is being created, updated, superseded, or deleted. TRIGGERS on "add rule", "new rule", "update the rule", "change the convention", "adjust the rule", "delete that rule", "make it a rule that…", "from now on we should…", "we should always/never…", or any request that would edit repo-governance/, AGENTS.md, CLAUDE.md, an agent or skill definition, repo-config.yml, a hook, or a CI workflow. Load it BEFORE editing any of those surfaces, not after.

C# coding standards from authoritative docs/explanation/software-engineering/programming-languages/c-sharp/ documentation

F# coding standards from authoritative docs/explanation/software-engineering/programming-languages/f-sharp/ documentation

AI agent development standards including frontmatter structure, naming conventions, tool access patterns, model selection, and reference documentation structure

Full validation methodology for project plans — structure, requirements (BRD/PRD), technical documentation, delivery-checklist executability, and 21 numbered validation rules (operational readiness, manual assertions, worktree/delivery-mode compliance, anti-hallucination, phase gates, specs/UI/learning coverage, Vercel MCP capability). Used by plan-checker.

Workflow pattern standards for creating multi-agent orchestrations including YAML frontmatter (name, goal, termination, inputs, outputs), execution phases (sequential/parallel/conditional), agent coordination patterns, and Gherkin success criteria. Essential for defining reusable, validated workflow processes.

Mechanics for social-linkedin-post-maker — the LinkedIn character-limit measurement rule, the no-vanity-metrics rule, the post file format, and the establish-window/gather/draft/measure/write workflow.

Repository-specific documentation authoring standards for docs-maker — the correctness/verification checklist, frontmatter template, and the AGENTS.md navigation-document philosophy. Complements the universal docs-applying-content-quality and docs-applying-diataxis-framework skills. Use when creating or editing docs/ content or AGENTS.md.