NomadicDaddy
Useraidd: local control panel for AI coding work. Plans, runs, audits, and reviews delegated work from your own machine with the agent CLIs you already use.
Categories
Indexed Skills (48)
bug2feature
Retrieve bug and feature reports from whatever intake a project uses, verify them against the codebase, and create correctly classified feature.json entries. Use when converting submitted reports into an actionable aidd backlog.
bun-guidelines
Bun (1.3.x) best practices for the package manager, text lockfile, direct TypeScript execution, Bun.serve routing, bun test, bundler, single-file executables, built-in APIs, Node.js compatibility, and Docker packaging. Use when writing, reviewing, or configuring Bun-based tooling or services.
changelog-rewrite
Rewrite a script-generated changelog into meaningful release history grouped by build phase, with aligned 0.x.y version references. Use when generated entries are noisy, repetitive, or carry inflated versions.
codebase-analysis
Run a broad aidd-oriented codebase analysis across architecture, performance, security, metadata health, and technical debt. Use for a full codebase review, health check, or technical-debt assessment of an aidd-managed project.
coderabbit-pr
Pull and remediate CodeRabbit feedback from a GitHub pull request, validate fixes, and commit without pushing. Use when addressing CodeRabbit findings on an existing PR.
coderabbit
Review pending changes with the CodeRabbit CLI: review the branch diff and working tree, fix findings judged real, dismiss false positives with justification, then run the quality gate. Use for CodeRabbit reviews of local changes.
commit-archaeology
Analyze an application's Git history for reversions, flip-flops, repeated rework, and unstable patterns. Use when investigating churn, indecision, or recurring refactors.
consolidate-features
Consolidate any aidd-managed application's `.aidd/features` by folding completed audit and remediation findings into their source features and removing redundant finding files. Use for feature cleanup, deduplication, or sprawl reduction.
cut-release
Cut a versioned release of a standalone repository: document the changes, run the gates, capture screenshots, land on main directly or through a pull request, tag, publish, and verify. Use to cut a release, ship a version, tag and publish, or release an app. Excludes the Spernakit template and its derived apps, which release through the dance.
deepreview
Perform an exhaustive, multi-perspective review of pending changes for correctness, security, maintainability, architecture, and stack compliance, then apply confirmed in-scope fixes. Use for deep, high-risk, release, or pre-merge reviews.
dependencies
Document the purpose, usage, necessity, and security/bundle impact of every project dependency in docs/dependencies.md. Use to audit, document, or review dependencies, or find unused or missing packages.
deployment-readiness
Prepare a managed application for its configured deployment target by adding missing deploy configuration, a deploy script, and `.aidd/deployment.md`; never deploy it. Use for deployment-readiness or deploy-configuration requests.
devdiary-update
Review recent activity across application repositories and propose development diary and story updates. Use to update the dev diary or devlog, or capture recent cross-project work.
diary-entry
Write one project daily-development diary entry from run history, iterations, Git history, features, and changelog evidence. Use when creating or refreshing .aidd/diary/YYYY/MM/DD.md.
doc2feature
Extract claims from a prose document, verify them against the live codebase, and create feature.json remediations for confirmed issues. Use when converting interviews, audits, analyses, or handoff notes into an evidence-backed aidd backlog.
docker-guidelines
Apply current Docker and container practices for secure, reproducible builds, Compose, BuildKit, caching, non-root execution, and supply-chain safety. Use when writing or reviewing Dockerfiles, Compose files, or container pipelines.
document-changes
Document any project's changes by updating its changelog, internal version, and feature metadata, then commit logical bundles without pushing or tagging. Use for change documentation, release notes, or version recording.
execute-audit
Run a current aidd audit against a local project, preserving reports under .aidd/audit-reports/ and actionable findings as .aidd/features/audit-*. Use to run a named aidd audit against a project and capture its findings.
feature-coverage-audit
Audit implemented features for natural documentation and complete `.aidd` feature metadata. Use to check documentation and feature parity, backfill missing feature JSON, or assess whether the app can be reconstructed from its recorded artifacts.
feature-review-all
Run the aidd-local feature-review sweep across selected applications with .aidd/features. Use when validating or repairing feature metadata across multiple application repositories.
feature-review
Review .aidd feature.json files against the target codebase for conflicts, contradictions, vagueness, and missing detail, then fix confirmed metadata issues. Use when validating feature quality before implementation or backlog planning.
frontend-design-sweep
Sweep every page and tab of a running application with one design-review subagent per surface, then consolidate the results into a single prioritized report. Use for a whole-app pass on how the UI could look cleaner, sleeker, and more consistent across screens.
gh-issue
Fetch a GitHub issue by number, verify it is a real and actionable issue, and fix it. Use when the user references a GitHub issue number and wants it triaged and resolved.
htmx-guidelines
htmx 4.0 development guidelines for attributes, explicit inheritance, triggers, targets, swap modes (incl. morph), hx-status error handling, forms, SSE/WebSocket streaming, extensions, security/CSP, response headers, and 2.x migration. Use when writing or reviewing hypermedia-driven UI built with htmx.
humanize-docs
Rewrite documentation and release prose to sound natural, concise, and expert-written. Use to remove AI-like wording, improve readability, or adapt tone; this is the prose style contract for other documentation skills.
hyperscript-guidelines
_hyperscript (0.9.93) scripting guidelines for event handlers, element references, element and global state, async fetch, DOM manipulation, htmx integration, and debugging. Use when writing or reviewing inline _hyperscript behavior.
loopover
Run one slash command or instruction once per matching file. Use when the same review, validation, or edit has to be applied across a set of files (e.g. every *.md, every feature.json) instead of one at a time.
mustache-guidelines
Mustache logic-less templating for server-rendered HTML fragments, including variables, escaping, sections, inverse sections, partials, and htmx integration. Use when writing or reviewing Mustache templates that render HTML for htmx swaps.
onboarding-interview
Generate a definitive handoff questionnaire for a project being inherited. Use when taking over or onboarding onto an unfamiliar project and wanting the key questions to ask before starting.
page-by-page
Ask one question of every page in a running application — one reviewer subagent per page — then consolidate the answers into a single prioritized report. Use for whole-app review passes on any theme: design polish, accessibility, mobile UX, copy, empty states, or performance.
page-header-audit
Find pages using manual heading markup instead of the app’s shared page-header component and migrate them to the standard pattern. Use for consistent page headers, PageHeader adoption, or standardizing display typography across pages.
promote-remediation
Convert a misclassified aidd remediation record into net-new feature work while preserving provenance and dependency references. Use when a remediation should be promoted or converted to a feature.
rbac
Reconcile RBAC documentation and the Roles page with application-specific resources. Use when role, permission, route, API, or resource coverage is incomplete or inconsistent.
refactor
Safe, context-aware code refactoring with impact analysis and validation. Use to refactor a specific file, function, or component with the change checked against its call sites and tests.
refresh-project-artifacts
Refresh every artifact recognized by aidd for one local application by following docs/reference/artifacts.md row by row. Use for full project-artifact maintenance, stale artifact reconciliation, or before relying on a project's blueprint, reports, and generated support files.
repo-governance-audit
Audit and optionally remediate GitHub and local repository governance across configured local roots, including branches, merge and security settings, Actions permissions, remotes, repository discovery, and documented exceptions. Use for repository policy checks.
12-factor-guidelines
Apply twelve-factor principles to backend services and deployment design, including configuration, backing services, statelessness, processes, logs, and portability. Use when designing, reviewing, or refactoring operational architecture.
check-settings
Compare an application's settings UI with its runtime configuration store. Use for settings or config audits, missing-setting checks, or read-only and exposure reconciliation.
commit-bundles
Split an aidd-managed app's dirty working tree into coherent commit bundles and commit only validated, documented changes. Use to commit a messy working tree, group changes into logical commits, or ship pending work for an aidd app.
convex-guidelines
Convex (1.42.x) coding guidelines for object function and validator syntax, the table-name DB API, indexed queries, pagination, file storage, scheduling, ESLint plugin rules, and TypeScript patterns. Use when writing or reviewing Convex backend functions, schemas, or actions.
defrag
Audit the stored memories for this root, removing outdated or duplicate entries. Use to clean up, compact, deduplicate, or defragment memories.
hygiene
Run the current aidd HYGIENE audit (canonical definition at <aidd-root>/audits/HYGIENE.md) against a project, following its phases, checklists, and report templates. Use for a code-hygiene audit, a cleanliness or dead-code sweep, or running HYGIENE on an app.
pode-guidelines
Pode (2.13.x) patterns for PowerShell web services, including server setup, module strategy, JWT auth, file-based routing, error handling, rate limiting, file logging, OpenAPI, and scheduled tasks. Use when writing or reviewing Pode API or Core services.
powershell-guidelines
Apply PowerShell 7.6 practices for cmdlet design, modules, error handling, and style, including Spernakit and Pode backend patterns. Use when writing or reviewing PowerShell scripts, modules, or Pode services.
prompt-guidelines
Apply coding-prompt engineering practices for task scoping, boundaries, phased workflows, stop conditions, output contracts, and context hygiene. Use when writing or reviewing prompts, specs, directives, recipe steps, or other agent instructions.
reality-check
Verify a file's actual implementation matches its inferred purpose. Use when reviewing unfamiliar files, debugging unexpected behavior, or validating code-to-intent alignment.
review-doc
Review a document for accuracy against the current application state. Use when docs are modified, referenced for accuracy, or during documentation audits.
review-or-create-doc
Review a document for accuracy against the current application state, or create it from the current state if it does not yet exist. Use when refreshing tracked documentation that may be missing.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.