By laurigates
Generate structured Markdown blog posts from git history using type-specific templates for project updates, retrospectives, and tutorials, with consistent style guides for scannable technical writing.
Consistent style guide for writing blog posts about projects and technical work. Supports quick updates, detailed write-ups, retrospectives, and tutorials. Designed for low-friction entry and easy scanning.
Create a blog post about your work with minimal friction. Gathers context automatically and provides structured templates to reduce blank-page anxiety.
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub laurigates/claude-plugins --plugin blog-pluginGit workflows - commits, branches, PRs, issue processing, auto-close detection, and repository management
Claude Code hooks for enforcing best practices and workflow automation
General utilities - fd, rg, jq, yq, nushell, shell, imagemagick, mermaid, d2
ComfyUI custom-node pack lifecycle - scaffold a pack, create + seed the repo, open the gitops adoption PR, publish to the Comfy Registry, and add README screenshots
Project infrastructure standards - comprehensive project configuration for pre-commit, CI/CD, Docker, testing, linting, formatting, and more
Manage velog.io blog posts from the terminal — create, edit, publish, and browse posts via the velog CLI.
Process skill for turning raw project data (research notes, session logs, drafts, code) into structured technical blog posts. Covers gathering, extraction, structure, and Astro frontmatter.
Write technical blog posts, tutorials, and documentation with Flatiron School's engaging teaching style. Turn complex topics into clear narratives.
Design fluency for frontend development. 1 skill with 23 commands (/impeccable polish, /impeccable audit, /impeccable critique, etc.) and curated anti-pattern detection.
Lazy senior dev mode. Forces the simplest, shortest solution that actually works: YAGNI, stdlib first, no unrequested abstractions.
Behavioral guidelines to reduce common LLM coding mistakes, derived from Andrej Karpathy's observations on LLM coding pitfalls