In the high-stakes world of generative AI, the divide between marginal gains and exponential productivity isn’t found in the model—it’s found in the architecture. This briefing explores the "Thin Harness, Fat Skills" framework, a design-forward approach to agentic AI that is currently enabling engineers to achieve 100x productivity. By shifting intelligence into reusable markdown "skill files" and keeping the execution harness lean, Singaporean firms can bypass the limitations of traditional prompt engineering to build systems that compound in value, transforming the city-state’s Smart Nation ambitions into a tangible, automated reality.
A Tuesday morning in Singapore’s Central Business District possesses a specific, rhythmic urgency. From the glass-walled heights of a Raffles Place skyscraper, one can observe the tectonic plates of global commerce shifting in real-time. Yet, beneath the polished surface of our "Smart Nation," a quieter, more profound revolution is occurring within the terminal screens of the city’s elite developers.
For years, the industry has been obsessed with the "Smarter Model." We awaited the next iteration of Claude or GPT with the bated breath once reserved for new iPhone launches. But as we move deeper into 2026, a disconcerting truth has emerged: two engineers can use the exact same model, yet one will be 100 times more productive than the other.
Steve Yegge recently posited that those using modern AI coding agents are "10x to 100x as productive as engineers using Cursor and chat today." To the uninitiated, this sounds like hyperbole—the kind of Silicon Valley bluster that typically dissolves under the humidity of the equator. But for those of us who have seen the internal mechanics of the latest agentic frameworks, the number is not just real; it is conservative.
The difference isn't intelligence. It’s architecture. And for Singapore—a nation defined by its lack of natural resources and its absolute reliance on human capital efficiency—mastering this architecture is no longer optional. It is the new baseline for survival.
The Claude Code Revelation: The Harness is the Product
The turning point occurred on March 31, 2026, when Anthropic inadvertently shipped the source code for Claude Code to the npm registry. For the global developer community, it was a "Pentagon Papers" moment for AI. Over 512,000 lines of code were laid bare, confirming what the most sophisticated builders had long suspected: the secret to agentic power isn't the model. It is the "harness" that wraps it.
In the context of Singapore’s burgeoning AI ecosystem—from the labs at A*STAR to the fintech hubs in Tanjong Pagar—the lesson is clear. We have been focusing on the wrong side of the equation. We have been trying to make the model "smarter" through increasingly complex prompts, when we should have been building a better scaffold for it to operate within.
The Claude Code leak revealed a system defined by live repository context, aggressive prompt caching, and structured session memory. It wasn't a "chat" interface; it was a high-performance engine designed to give the model exactly what it needed, exactly when it needed it, without drowning it in the "context bloat" that plagues amateur implementations.
The Five Definitions of the New AI Architecture
To understand how to achieve 100x productivity, we must move beyond the vocabulary of the "chatbot." We need a new lexicon for agentic design. This framework fits on an index card, yet it governs the most powerful AI systems currently in operation.
1. Skill Files: The Markdown as Method Call
The most significant shift in 2026 is the death of the "one-shot prompt." In its place, we have the Skill File. This is a reusable Markdown document that teaches the model a process, rather than a specific task.
Think of a skill file as a method call in traditional programming. It defines the logic and the steps, but it remains agnostic about the data. For a Singaporean legal firm, a skill might be /review-contract. The skill file doesn't contain a contract; it contains the seven-step intellectual process of a senior partner: identify jurisdictions, flag indemnity loopholes, cross-reference with MAS (Monetary Authority of Singapore) guidelines, and synthesise a risk profile.
The beauty of the skill file is its versatility. Point it at a lease agreement for a shophouse in Geylang, and it acts as a real estate lawyer. Point it at a cross-border M&A document, and it becomes a corporate strategist. This is not prompt engineering; it is software design where Markdown is the language and human judgment is the runtime.
2. The Thin Harness: The Virtue of Minimalist Design
In Singaporean architecture, we often speak of "tropical minimalism"—designs that provide maximum utility with minimum obstruction. The Harness should follow the same principle.
The harness is the program that runs the LLM. It handles the loop, manages files, and enforces safety. The "Thin Harness" philosophy dictates that the harness should be as simple as possible—ideally around 200 lines of code.
The "Fat Harness" is the enemy of productivity. You see it in over-engineered systems bloated with 40+ tool definitions that eat up the context window and introduce 15-second latencies for simple tasks. A thin harness uses purpose-built, narrow tools. Instead of a slow, multi-purpose browser tool, it uses a high-speed CLI that performs specific operations in milliseconds. In the race for 100x productivity, speed is the only metric that matters.
3. Resolvers: The Traffic Controllers of Context
One of the primary reasons AI fails in complex environments is "context pollution." The model is given too much irrelevant information, causing its attention to degrade. Resolvers fix this by acting as a routing table for context.
A resolver ensures the model only sees what it needs. If a developer in a Singaporean gaming studio is changing a game mechanic, the resolver automatically loads the relevant documentation and evaluation suites. The model doesn't have to "remember" the rules; the resolver provides them at the precise moment of intervention. This allows for massive repositories of knowledge—tens of thousands of lines—to be accessible on demand without ever overwhelming the model’s immediate working memory.
4. Latent vs. Deterministic: Bridging Logic and Trust
This is where most AI implementations in the local sector stumble. They fail to distinguish between Latent Space (where the model reasons, synthesises, and interprets) and Deterministic Space (where code, math, and databases live).
An LLM is magnificent at deciding how to seat ten diverse delegates at a Shangri-La Dialogue dinner to ensure optimal diplomatic flow—that is a latent problem involving social nuance. However, asking an LLM to calculate the most efficient flight paths for 800 delegates is a recipe for hallucination—that is a deterministic, combinatorial optimisation problem.
The 100x engineer is ruthless about this distinction. They push intelligence up into the latent skill files and push execution down into deterministic tools. They never ask the model to do math; they ask the model to write the Python script that does the math.
5. Diarization: The Analyst’s Brief
Finally, we have Diarization. This is the process of the model reading vast amounts of unstructured data and distilling it into a structured profile—a single page of judgment.
In a city drowning in data—from ERP systems to Slack channels—diarization is the killer app. It is the difference between a "search" (which returns snippets) and an "analysis" (which returns insight). A diarized profile of a project doesn't just list the facts; it notes the contradictions, the shifts in tone over time, and the underlying risks. It is the AI equivalent of a senior civil servant’s briefing note.
The Singapore Lens: Scaling Beyond the Workforce Bottleneck
For Singapore, the "Thin Harness, Fat Skills" architecture isn't just a technical preference; it is a national imperative. We face a chronic labor shortage and a rapidly aging population. Our traditional response has been to import talent or work longer hours. AI agents offer a third way: the ability to scale intelligence without scaling headcount.
Imagine a government agency tasked with processing thousands of grant applications. The traditional "Fat Harness" approach would involve building a complex, rigid software platform. The "Thin Harness" approach involves a lean system running a "Grant Evaluator" skill file. This skill file can be updated in minutes by a policy officer writing in plain Markdown—no coding required. As the policy changes, the skill file is updated, and the entire system instantly learns the new rules.
In our CBD walk-through, we see the potential everywhere. The boutique wealth management firms in Shenton Way can use diarization to monitor global sentiment on Singaporean REITs. The logistics giants in Jurong can use resolvers to ensure their AI agents are always operating under the latest maritime safety regulations.
Case Study: The Learning Loop in Action
Consider a large-scale innovation summit in Singapore, such as SWITCH (Singapore Week of Innovation and Technology). With 10,000 attendees, the logistics of matching founders to investors are staggering.
A "Thin Harness" system handles this with ease:
Enrichment: A skill called
/enrich-profilepulls public data, social signals, and previous pitch decks.Diarization: The model reads these sources and identifies the "gap"—perhaps a founder says they are building "FinTech," but their GitHub history shows they are actually building a core database engine.
Matching: A matching skill treats the diarized profile as a "method call." It isn't just looking for keywords; it's looking for "sector affinity" and "founder temperament." It might decide to pair two founders because they are solving similar scaling problems, even if their industries are different.
The Learning Loop: After the event, an
/improveskill reads the feedback. If attendees felt the meetings were "too corporate," the model identifies the pattern and rewrites the matching skill to prioritise "serendipity" and "underground tech" in the next iteration.
The system compounds. It gets smarter without a single line of traditional code being rewritten. This is how you achieve Yegge’s 100x. You aren't just building a tool; you are building a system that learns how to use its tools better every single day.
Permanent Upgrades: The End of One-Off Work
The most powerful command a Singaporean manager can give their AI today is this: "You are not allowed to do one-off work."
In the "Thin Harness" paradigm, every task must be codified into a skill file. If an agent is asked to perform a market analysis of the HDB resale market, it must first do it manually, show the output, and once approved, save that process as a permanent skill.
This creates a "permanent upgrade" to the organisation. Unlike a human employee who might leave for a competitor in Hong Kong or Sydney, the skill file stays. It never degrades. It runs at 3 AM. And when the next, more powerful model is released—be it Claude 4 or GPT-6—every single skill file in your library instantly receives a "brain transplant," becoming more nuanced and capable without you changing a single word of the process.
Key Practical Takeaways
Thin the Harness: Audit your current AI implementations. If your "tools" and "instructions" are eating more than 20% of your context window, you are building a "Fat Harness." Strip it back to the essentials.
Codify Judgment in Markdown: Move away from complex system prompts. Start building a library of
.skillfiles that describe processes and judgment logic in structured Markdown.Embrace the Deterministic: Never ask an LLM to do what a 10-line Python script or a SQL query can do. Use the AI for synthesis (Latent Space) and external tools for execution (Deterministic Space).
Build the Learning Loop: Implement a process where the output of your agents is periodically reviewed by an "Improvement Skill" that rewrites the original skill files based on performance data.
Focus on Diarization: Stop using AI for simple search. Use it to build deep, structured profiles of your data—whether that’s customer behavior, codebases, or market trends.
Frequently Asked Questions
How does a "Skill File" differ from a standard System Prompt?
While a system prompt is a static set of instructions, a Skill File is designed to be a modular, reusable "method." It often takes parameters (e.g., TARGET, DATASET) and is invoked by a resolver only when needed. This prevents context bloat and allows for much more complex, multi-step reasoning processes than a single prompt can handle.
Is Singapore’s infrastructure ready for this level of AI agentic integration?
Absolutely. Singapore’s high-speed connectivity and the government’s "AI Verify" framework provide the perfect sandbox. The challenge is not infrastructure, but "architectural literacy"—moving the local workforce from "users of AI" to "architects of agentic systems."
What is the biggest risk of the "Thin Harness, Fat Skills" approach?
The primary risk is "latent drift"—where the model's interpretation of a skill changes slightly as the underlying model is updated. This is why the "Deterministic Layer" (evals and tests) is crucial. You must have deterministic checks to ensure the latent reasoning remains within the desired bounds.