Automated summary
Preloads dancing-bear repository context at session start by running ./bin/llm familiar and pointing Claude at the internal docs and available CLIs.
Strengths
- One-command bootstrap: the returned YAML capsule carries skip paths, key CLIs and the read-only familiarization contract
- Deliberate progressive disclosure: .llm/CONTEXT.md, PATTERNS.md and MIGRATION_STATE.md load only on demand, and the domain map is generated rather than preloaded
- Explicit skip list (.venv/, .git/, maker/, _disasm/, out/, backups/) keeps context from being wasted on heavy directories
- Discovers tooling through agentic schemas (--agentic --agentic-format yaml) instead of --help, keeping output compact and machine-readable
Limitations
- Tied to the dancing-bear repo and its ./bin/llm binary; it does nothing on any other project
- Assumes the local layout and .llm/*.md files exist and are current, otherwise the capsule is empty or misleading
- Does not explain the code itself, only where to read it, so it is no substitute for exploring the source
At the very start of a session on the dancing-bear repo, before answering a request or making any change.
On a different codebase, or when the ./bin/llm tooling and .llm/ directory are not present in the environment.
Security analysis
SafeThe skill only preloads local repository context via repo-local CLIs and read-only inspection. It does not instruct destructive commands, secret exfiltration, obfuscated payloads, or safety disabling. Bash usage is limited to legitimate project introspection.
No concerns found
How this analysis is madeExamples
/familiarize — get oriented in this repo before I ask you to change anything.Get familiar with this repo again; I've been away for a week and want you re-oriented before we touch the mail-assistant.Run /familiarize, then load the agentic schema for calendar-assistant only and tell me which subcommands exist.name: familiarize description: Preload repo context for the dancing-bear personal-assistants codebase. Use when the user runs /familiarize, says "get familiar with this repo", or starts a new session and wants Claude oriented before making changes. allowed-tools: Bash, Read, Glob skills:
- dancing-bear-rules
Project Familiarization
Load context about dancing-bear at session start.
When to Use
- Session start — run before responding to first request
- Context refresh — when you need to re-orient
- Feature discovery — exploring what tools are available
Run Familiarize
./bin/llm familiar --stdout
This returns a YAML capsule covering:
- Skip paths and heavy files to avoid
- Key CLIs and agentic schema pointers
- Familiarization contract (read-only rules)
Deep Dive (On-Demand Only)
Load these only when the task requires deeper understanding:
| File | When to Load |
|------|-------------|
| .llm/CONTEXT.md | Architecture questions, system overview |
| .llm/MIGRATION_STATE.md | In-flight work, current status |
| .llm/PATTERNS.md | Implementing features, copy-paste templates |
| .llm/FAMILIARIZE_CORE.md | Familiarization contract details |
Generate on demand (never preload):
./bin/llm domain-map --stdout # directory structure deep dive
Tool Discovery
For CLI capabilities, use agentic schemas (never --help):
./bin/<assistant> --agentic --agentic-format yaml --agentic-compact
Primary surfaces: mail-assistant, calendar-assistant, schedule-assistant, phone-assistant.
Load only the wrapper(s) relevant to the current task.
After Familiarize
You should know:
- What the project does (unified personal-workflow CLIs: mail, calendar, schedule, phone, WhatsApp)
- How to run CLIs (
./bin/<assistant> <subcommand> <flags>) - Where to find patterns (
.llm/PATTERNS.md) - Paths to skip (
.venv/,.git/,.cache/,maker/,_disasm/,out/,_out/,backups/) - Available skills (
/familiarize,/dancing-bear-rules, etc.)
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/familiarize-with-dancing-bear-repo-ms1aw4f5/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/familiarize-with-dancing-bear-repo-ms1aw4f5' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/familiarize-with-dancing-bear-repo-ms1aw4f5/download' --output '.skill-downloads/familiarize-with-dancing-bear-repo-ms1aw4f5/SKILL.md.part' && mv '.skill-downloads/familiarize-with-dancing-bear-repo-ms1aw4f5/SKILL.md.part' '.skill-downloads/familiarize-with-dancing-bear-repo-ms1aw4f5/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Bash, Read, Glob
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/familiarize-with-dancing-bear-repo-ms1aw4f5/SKILL.md' && test -s '.skill-downloads/familiarize-with-dancing-bear-repo-ms1aw4f5/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/familiarize' && cp -R '.skill-downloads/familiarize-with-dancing-bear-repo-ms1aw4f5' '.claude/skills/familiarize'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/familiarize-with-dancing-bear-repo-ms1aw4f5'openskills read 'familiarize-with-dancing-bear-repo-ms1aw4f5'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/familiarize-with-dancing-bear-repo-ms1aw4f5/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.