lexburner/skill-collection

Overview

This skill captures the Kirito technical-blog writing style and provides concrete guidance to produce personable, practice-first, and opinionated technical posts. It helps transform raw technical content into readable blog articles that balance storytelling, code clarity, and candid experience sharing. Use it to keep a consistent voice that is informal, confident, and useful.

How this skill works

The skill defines voice, structure, and narration techniques: first-person tone, light humor, strategic suspense, and habitually sharing pitfalls and benchmarks. It prescribes templates for intro, body, and conclusion, plus rules for code samples, comparisons, and citation blocks. Applying the rules converts drafts or notes into Kirito-style posts or rewrites existing articles to match the persona.

When to use it

• Writing a new technical blog post, tutorial, or public article with a personal voice
• Polishing or rewriting an existing draft to be more engaging and opinionated
• Converting technical notes, reports, or talk slides into a readable blog
• Preparing post-mortems, benchmark writeups, or experience-sharing pieces
• Creating content for newsletters or public WeChat/Medium-style posts

Best practices

• Write in first person and keep the tone conversational—don’t be overly formal
• Start with a short, human introduction: motivation, story, or a concrete problem
• Show actual code and benchmark data; explain why and how, not just what
• Share mistakes and lessons learned openly—readers value candid pitfalls
• Use brief analogies or life metaphors to clarify complex concepts
• End with a concise summary and a small actionable suggestion or sign-off

Example use cases

• Turn a README or technical notes into a reader-friendly tutorial with examples
• Refactor a dry documentation section into a narrative-driven blog post
• Write a performance comparison article with benchmarks and clear takeaways
• Compose a contest post-mortem that lists optimizations, pitfalls, and gratitude
• Produce a practical how-to guide that includes runnable code and step checks