add-pattern
The add-pattern skill documents newly discovered Langroid design patterns by creating entries in a skills catalog with clear problem descriptions and matching criteria, then writing detailed pattern documentation with implementation examples, problem context, solutions, complete code samples, key points, and usage guidelines in a standardized format.
git clone --depth 1 https://github.com/pchalasani/claude-code-tools /tmp/add-pattern && cp -r /tmp/add-pattern/plugins/langroid/skills/add-pattern ~/.claude/skills/add-patternSKILL.md
# add-pattern ## Instructions When you learn a new Langroid design pattern, do the following: 1. Add an entry in the sibling `patterns/SKILL.md` file in the appropriate category section, containing a DESCRIPTION of the goal of the pattern (i.e. what it enables you to implement), accompanied by a `- Reference:` pointer to a markdown DOCUMENT in the `patterns/` directory. IMPORTANT - The DESCRIPTION should be clear enough that future YOU can effectively use it to MATCH design problems you may encounter in future. 2. In that DOCUMENT, describe the idea of the implementation along with code examples. Follow the format of existing pattern files (Problem, Solution, Complete Code Example, Key Points, When to Use).
Literature-backed English technical-prose writing rules (agent-style, 21 rules). Its lane is FORMAL technical prose (papers, design docs, proposals, READMEs, commit messages). Use ONLY when the user explicitly asks for agent-style by name (e.g. "apply agent-style", "write/revise this per agent-style rules", "iterate until agent-style clean"). NOT for de-AI-ing casual or voiced text — use remove-ai-patterns for that. Do not auto-trigger for ordinary prose or documentation tasks.
Audit and rewrite content to remove AI writing patterns ("AI-isms"). Use this skill when asked to "remove AI-isms," "clean up AI writing," "edit writing for AI patterns," "audit writing for AI tells," or "make this sound less like AI." Supports a detect-only mode, an edit-in-place mode for files, an optional voice profile (casual / professional / technical / warm / blunt), and an iterate-to-convergence pass.
Use this when user wants you to walk through (code or text) files in a EDITOR to either explain how some code works, or to show the user what changes you made, etc. You would typically use this repeatedly to show the user your changes or code files one by one, sometimes with specific line-numbers. This way the user is easily able to follow along in their favorite EDITOR as you point at various files possibly at specific line numbers within those files.
>-
>-
Log the work segment that you did after the last work log until now in a
Create a markdown document that describes a specific task along with
>-