Packs
2 packsResults for “technical-blog”
9 skillstechnical-blog-writing
Write developer-focused technical blog posts with structured templates, code formatting rules, and audience-specific guidance for tutorials, deep dives, postmortems, and architecture posts.
584
blog-writing-specialist
Comprehensive blog writing skill that handles technical blog posts, personal voice writing, brain dump transformation, and category-aware AEO-optimized content. Use when: (1) writing, editing, or proofreading a blog article or post, (2) transforming unstructured brain dumps into polished posts, (3) writing in specific personal voices (Jarad, Nick Nisi), (4) creating category-aware technology/company/product posts, (5) building tutorials, deep dives, postmortems, benchmarks, or architecture posts, (6) writing engineering blogs, dev blogs, programming blogs, coding tutorials, or documentation posts. Triggers: blog post, blog writing, technical blog, dev tutorial, brain dump, article, content writing, developer article, engineering blog, programming blog, coding tutorial, documentation post, technical writing, blog editing, proofreading, developer content
88 · bundle
More results
blog-writing-guide
Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar.
845
tech-impl-deep-dive-writer
Writes mechanism-first technical implementation deep-dive articles that explain design intent, data flow, trade-offs, and operations, with code locations as supporting evidence.
0 · bundle
retrospective
Creates a technical journey retrospective document from a coding session, capturing decisions, tradeoffs, and debugging moments in a developer blog post style.
3 · bundle
brag-sheet
Turn engineering work into evidence-backed impact statements for performance reviews, self-reviews, promotion packets, and weekly updates by mining Copilot CLI session logs, git history, and GitHub PRs.
36.2k
tech-debt
Scan, prioritize, and report technical debt. Usage: /tech-debt <scan|prioritize|report> [options]
0
deck-tech-sharing
Creates a tech sharing deck for internal engineering talks with GitHub-dark theme and JetBrains Mono code blocks.
· bundle
qa
Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only. (gstack) Voice triggers (speech-to-text aliases): "quality check", "test the app", "run QA".
0