<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Skill Design on Chuanxilu for Skilled Homo sapiens</title><link>https://blog.chuanxilu.net/en/tags/skill-design/</link><description>Recent content in Skill Design on Chuanxilu for Skilled Homo sapiens</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 21 May 2026 11:00:00 +0800</lastBuildDate><atom:link href="https://blog.chuanxilu.net/en/tags/skill-design/index.xml" rel="self" type="application/rss+xml"/><item><title>The Invisible Blank Layer</title><link>https://blog.chuanxilu.net/en/posts/2026/05/tdd-pipeline-phase7-invisible-gap/</link><pubDate>Thu, 21 May 2026 11:00:00 +0800</pubDate><guid>https://blog.chuanxilu.net/en/posts/2026/05/tdd-pipeline-phase7-invisible-gap/</guid><description>Phase 6 drills every bug to root cause. But it doesn&amp;#39;t scan for shared patterns across bugs, unchecked component gaps, or execution order flaws. That&amp;#39;s Phase 7&amp;#39;s job. In small systems it catches more bugs. In large systems, the same findings point to architectural evolution. Phase 7 doesn&amp;#39;t make architecture decisions — it provides the scarcest input for them: evidence-based problem localization.</description></item><item><title>Using the Method to Improve the Method</title><link>https://blog.chuanxilu.net/en/posts/2026/05/tdd-pipeline-v07-refinement-experiment/</link><pubDate>Wed, 20 May 2026 10:00:00 +0800</pubDate><guid>https://blog.chuanxilu.net/en/posts/2026/05/tdd-pipeline-v07-refinement-experiment/</guid><description>I built a ruler. The ruler measured &amp;#39;redundancy is harmful.&amp;#39; Then I used that ruler to trim the ruler&amp;#39;s own redundancy. I deleted the operational steps from my AI skill files, keeping only principles and counterexamples. The model reconstructed the deleted steps on its own — output quality didn&amp;#39;t drop.</description></item><item><title>What a Failed Experiment Got Right</title><link>https://blog.chuanxilu.net/en/posts/2026/05/tdd-pipeline-v08-failed-experiment-discovery/</link><pubDate>Tue, 19 May 2026 18:00:00 +0800</pubDate><guid>https://blog.chuanxilu.net/en/posts/2026/05/tdd-pipeline-v08-failed-experiment-discovery/</guid><description>I tried refining the pre-release testing phase of my TDD Pipeline by replacing step-by-step instructions with principles. The refined version failed at its core job. But comparing where it failed against where it unexpectedly succeeded revealed that individual defect diagnosis alone wasn&amp;#39;t enough — it needed a systematic scanning layer on top.</description></item></channel></rss>