task-tracking-dots-html
Manages task tracking with the HTML-backed Dots fork from Randroids-Dojo/dots-html. Use when tracking work items across sessions with dot-html CLI files stored as .html documents.
What this skill does
# Task Tracking with HTML Dots
Use the `dot-html` CLI from `Randroids-Dojo/dots-html` to track work items across sessions. This fork stores dots as `.html` documents under `.dots/`.
## Preflight
Check for the CLI:
```bash
command -v dot-html >/dev/null 2>&1 && dot-html --version
```
If `dot-html` is missing, install this fork:
```bash
plugins/task-tracking-dots-html/scripts/install-html-dots.sh
```
When installed from a global skill, run the script from the installed skill directory. If the release has no matching binary asset for the current OS/architecture, the script clones `https://github.com/Randroids-Dojo/dots-html` and builds with Zig.
## Session Workflow
At the start of every session:
```bash
dot-html ls
dot-html ready
```
Before starting work:
```bash
dot-html on <id>
```
After completing work:
```bash
dot-html off <id> -r "What was done"
```
Never leave completed tasks open. Close with a short reason.
## Creating Dots
```bash
dot-html "Fix the bug"
dot-html add "Design API" -p 1 -d "Details"
dot-html add "Subtask" -P dots-1
dot-html add "After X" -a dots-2
```
## Inspecting Work
```bash
dot-html ls
dot-html ready
dot-html show dots-1
dot-html tree
dot-html find "query"
```
## File Storage
New dots are stored as HTML files:
```text
.dots/
dots-example-1234abcd.html
dots-parent-2345bcde/
dots-parent-2345bcde.html
dots-child-3456cdef.html
```
The CLI owns these files. Prefer `dot-html` commands for changes so status, dependencies, archive moves, and parent-child paths stay consistent.
Related in Web Dev
generating-lwc-components
IncludedLightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.
document-processor-api
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
nutrient-document-processing
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.
accelint-nextjs-best-practices
IncludedNext.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.