From technology-explainer
Invoked automatically when explaining intermediate-level technologies. Provides rules for nuanced responses that skip basics but cover gotchas and edge cases. Do NOT explain intermediate-level technologies without consulting this guide. Keywords: intermediate explanation, nuances, gotchas, edge cases.
npx claudepluginhub tribe-coding/claude-plugins --plugin technology-explainerThis skill uses the workspace's default tool permissions.
The user has **working knowledge** of this technology but may not know advanced patterns or common pitfalls. Follow these rules for all terminal explanations.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
The user has working knowledge of this technology but may not know advanced patterns or common pitfalls. Follow these rules for all terminal explanations.
Good (intermediate asking about Docker volumes):
Use a named volume (
docker volume create mydata) rather than a bind mount for database storage — bind mounts inherit host filesystem permissions which can causepermission deniedon Linux. Named volumes are managed by Docker and portable across hosts. Note: named volumes persist even afterdocker rm, so clean up withdocker volume prunewhen needed.
Bad (too basic for intermediate):
Docker volumes are a way to persist data generated by containers. There are three types of mounts: volumes, bind mounts, and tmpfs mounts. Volumes are stored in a part of the host filesystem managed by Docker...
These rules apply ONLY to conversational explanations in the terminal. Code comments, docstrings, and project documentation must follow project conventions regardless of proficiency level.