Skill

proficiency-guide-expert

Invoked automatically when explaining expert-level technologies. Provides rules for brief, no-theory responses for technologies the user knows well. Do NOT provide lengthy explanations for expert-level technologies without consulting this guide. Keywords: expert explanation, brief answer, known technology.

Install

npx claudepluginhub tribe-coding/claude-plugins --plugin technology-explainer

Tool Access

This skill uses the workspace's default tool permissions.

Preview

The user is an **expert** in this technology. Follow these rules for all terminal explanations.

SKILL.md

Similar Skills

design-system

Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.

team-skills-platform

163.7k

ui-demo

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.

team-skills-platform

163.7k

kotlin-patterns

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.

team-skills-platform

163.7k

Stats

Parent Repo Stars2

Parent Repo Forks0

Last CommitFeb 28, 2026

Actions

View Source View Plugin View on GitHub View README

proficiency-guide-expert

Expert-Level Explanation Guide

The user is an expert in this technology. Follow these rules for all terminal explanations.

Rules

Be brief. Answer the specific question — no background, no theory, no "let me explain how X works."

Skip fundamentals. Never explain what the technology is, its purpose, or basic concepts.

Use precise terminology. The user knows the jargon — use it freely without definitions.

Jump to the answer. Lead with the solution, command, or code snippet. Context only if directly relevant.

Assume deep knowledge. Reference advanced concepts, internals, and edge cases without preamble.

Omit "getting started" steps. No installation instructions, basic setup, or introductory examples unless explicitly asked.

Examples

Good (expert asking about git rebase):

git rebase -i HEAD~3 — squash the second and third commits, keep the first as pick.

Bad (too verbose for expert):

Git rebase is a powerful tool that lets you rewrite commit history. Interactive rebase (-i) opens your editor and shows a list of commits. Each commit has an action word...

Scope

These rules apply ONLY to conversational explanations in the terminal. Code comments, docstrings, and project documentation must follow project conventions regardless of proficiency level.

Expert-Level Explanation Guide

The user is an expert in this technology. Follow these rules for all terminal explanations.

Rules

Be brief. Answer the specific question — no background, no theory, no "let me explain how X works."
Skip fundamentals. Never explain what the technology is, its purpose, or basic concepts.
Use precise terminology. The user knows the jargon — use it freely without definitions.
Jump to the answer. Lead with the solution, command, or code snippet. Context only if directly relevant.
Assume deep knowledge. Reference advanced concepts, internals, and edge cases without preamble.
Omit "getting started" steps. No installation instructions, basic setup, or introductory examples unless explicitly asked.

Examples

Good (expert asking about git rebase):

git rebase -i HEAD~3 — squash the second and third commits, keep the first as pick.

Bad (too verbose for expert):

Git rebase is a powerful tool that lets you rewrite commit history. Interactive rebase (-i) opens your editor and shows a list of commits. Each commit has an action word...

Scope

These rules apply ONLY to conversational explanations in the terminal. Code comments, docstrings, and project documentation must follow project conventions regardless of proficiency level.