73nko/career-vault / .agents/skills/source-command-concept
source-command-concept
UnverifiedBootstraps a concept note. Skeleton + interview Qs; user fills substance. Refuses to write content the user hasn't engaged with.
source-command-concept
Use this skill when the user asks to run the migrated source command concept.
Command Template
The user wants to create a concept note for:
${1}
Hard rule
You do not write the substance of the concept for the user. Writing a complete concept note from your training data is exactly the "reading about ≠ learning" anti-pattern flagged in the master plan. Your job is to build a good prompt for the user to fill in, not to fill it in for them.
The only sections you may pre-fill:
- The frontmatter / tags (per template).
- The list of interview questions this concept tends to attract (this is what the user is preparing for — the questions are the prompts).
- Pointers to related concepts that already exist in the vault (search
03_Concepts/for adjacency). - A one-line stub in "Definición" — and only as a placeholder for the user to rewrite.
Everything else stays as template placeholders.
Flow
- Figure out which domain folder this belongs in: Algorithms, Frontend, Backend, JavaScript, TypeScript, Patterns, Performance, SystemDesign, Books. If ambiguous, propose two and let the user pick.
- Search
03_Concepts/<Domain>/to confirm no existing note for this topic. If one exists, surface it and ask whether the user wants to extend it instead of creating a new one. - Generate 5-8 interview questions that this concept tends to attract, tilted toward Staff-level depth (not "what is X" but "when would you not use X", "what does X cost at 10x scale", "what's the trade-off between X and Y").
- Find 2-4 related existing notes in the vault to link.
- Create the note at
03_Concepts/<Domain>/<Topic>.mdusing the template at99_Templates/Concept.md. Use Templater syntax where the template does. Leave Definición, Por qué importa, Cómo funciona, Ejemplo, and Trade-offs as empty headings with a<!-- TODO -->marker. - Update
03_Concepts/<Domain>/00_MOC_<Domain>.mdto add a link to the new note under the appropriate subsection.
After saving
Tell the user, in 2-3 sentences:
- The 1 interview question this note should be able to answer in 2 minutes when finished.
- One specific exercise they can do to actually learn the concept rather than just summarize it (build a small thing, walk through a failure case, explain it to a rubber duck in their own words).
Anti-patterns to refuse
If the user asks: "just write the concept for me" or "give me the full explanation of X" — refuse, and reread the second rule of the master plan back to them: "Confundir 'leer sobre algo' con 'aprenderlo'." Offer to help them learn the concept instead (Socratic Q&A, exercise design, critique of their draft).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |