标签 · Framework — Glean

Recent picks

12picks · chronological

07-14

Deep Comparison of AI Agent Skill Frameworks: Matt Pocock Skills, Superpowers, and Agent Skills

This article systematically compares three major AI agent skill frameworks: Matt Pocock Skills (engineering practice), Superpowers (community workflow), and Agent Skills (production lifecycle). It evaluates them across positioning, skill granularity, learning curve, token consumption, tool support, and community size, offering selection recommendations for individuals, small teams, mid-large teams, and enterprises. Key findings: Matt Pocock Skills excels at deep alignment and architecture optimization, Superpowers provides end-to-end workflows with a rich plugin ecosystem, and Agent Skills enforces verification gates and anti-rationalization for quality. It also suggests combination strategies. Suitable for developers and tech leads choosing a workflow framework for AI coding assistants.

www.besthub.dev · 8 min · Agent Engineering · Ai Tooling · Comparison

07-04

Switching from Superpowers to mattpocock/skills: Less Token Waste, More Control

The author shares a real-world comparison between Superpowers and mattpocock/skills, explaining why they switched. Superpowers uses hooks to enforce a rigid workflow, which is helpful for novices but often overcomplicates simple tasks and burns excessive tokens. mattpocock/skills takes a 'real engineer' approach, giving control back to the user via explicit commands like /grill-with-docs, /to-prd, /to-issues, and /implement. Key advantages: lower token consumption, built-in debugging (/tdd, /diagnosing-bugs), model handoff (/handoff), and architecture refactoring (/improve-codebase-architecture). The author pairs these skills with Fable 5 and Codex 5.5 models, storing PRDs and issues on GitHub for traceability. A candid take for engineers evaluating agent frameworks and tooling.

justinyan.me · 3 min · Agent Engineering · Claude Code Marketplace · Framework

06-05

AI Amplifies Output, Not Input: My /learn Workflow for Deep Technical Dives

The author shares a personal workflow for deep learning in the AI era: treat learning like coding, structured as collect → filter → outline → draft → AI-assisted tightening → self-review. The core argument is that AI's real value lies in amplifying your output, not in summarizing input. Using a recent deep dive into LLM training as an example, the post introduces the /learn skill in the open-source Waza toolkit to industrialize this process. Recommended for engineers wondering how to maintain depth while leveraging AI.

tw93.fun · 2 min · AI · Framework

06-05

Building an AI Second Brain with Claude and Obsidian: The Complete Tutorial

A hands-on tutorial on connecting Claude to an Obsidian vault, turning your notes into a queryable knowledge engine that reasons over your own context. Covers vault structure (PARA method), AI-first note design, three Claude integration methods (Projects upload, Claude Code direct access, MCP servers), and five ready-to-use workflows (weekly digest, research synthesis, idea connection, knowledge gap auditing, daily briefing). Best for developers, researchers, and knowledge workers building a persistent personal knowledge system.

x.com · 13 min · Agents · AI · Framework

06-04

Multi-Agent Coordination Patterns: Five Approaches and When to Use Them

This post systematically covers five multi-agent coordination patterns: generator-verifier, orchestrator-subagent, agent teams, message bus, and shared state. For each, it explains the mechanism, where it works well, and known struggles (e.g., verifier quality depends on explicit criteria, orchestrator becomes information bottleneck, agent teams require independent subtasks, message bus tracing is hard, shared state risks reactive loops). It recommends starting with the simplest pattern and evolving based on where it struggles, with decision guides comparing patterns side by side. Suitable for engineering teams building multi-agent systems.

claude.com · 19 min · Agents · AI · Framework

06-01

How to build your own agent harness???

iii proposes an alternative to monolithic agent frameworks: decomposing the harness into a set of independent workers on a shared WebSocket engine. Each of the 15 responsibilities (turn orchestration, auth, policy, approval, session, etc.) is a separate worker that registers functions and triggers on a common bus via iii.trigger(). The architecture makes every layer replaceable—swap the model catalogue by writing a worker that registers models::list, add a provider with provider::<name>::stream, without touching the rest of the stack. The post walks through the turn loop in detail, explaining how provisioning, streaming, tool execution, approval gating, and teardown work across workers. Concrete replacement examples include model catalogue, credential store, approval UI, and policy engine. The entire harness is open source (github.com/iii-hq/workers), with all workers operating under the same protocol, yielding full OpenTelemetry tracing. The key insight: 'build your own harness' means swapping workers, not forking a framework, enabling a slider between thin and thick setups.

x.com · 20 min · Agents · Framework · Workers

05-29

Claude Code Dynamic Workflows: A New Primitive That Moves Orchestration Into Code

Anthropic introduces Dynamic Workflows, a primitive that turns task orchestration into JavaScript scripts executed by a deterministic runtime. The script manages loops, branching, and intermediate results, so only the final answer enters the main Claude context—solving the bottleneck of context overflow and attention dilution when coordinating hundreds of parallel tasks. A deep dive into architecture, primitives, and execution model is paired with a real-world Bun-to-Rust migration (11 days, 750K lines, 99.8% test pass) and a personal 133-session analysis. Comparisons with n8n/Coze/Dify show Workflow's advantage: Turing-complete code offers more expressiveness than visual DAGs, and the orchestration can be generated on‑the‑fly by a model. It shines for codebase audits, large migrations, and adversarial verification but comes with high token costs and current preview limits. Target audience: engineers tackling massive, automated coding tasks.

x.com · 19 min · Agents · AI · Framework

05-29

Context Engineering Is Replacing Prompt Engineering. Here's How It Works

The author argues that prompt engineering is giving way to 'context engineering'—building the environment of information (identity, knowledge, memory, tools, processes) that enables a model to produce consistent results with minimal prompting. A five-layer framework is detailed, with practical steps for Claude users: set custom instructions, upload knowledge files, actively craft memory, connect MCP tools, and encode processes as Skills. The piece is opinionated and lacks empirical evidence but offers actionable guidance for those heavily using Claude.

x.com · 12 min · AI · Framework · LLM

05-29

Organizational Structure for AI-First in the Harness Era

A podcast interview with Creao's founders explores Harness Engineering—building self-healing, self-improving systems around LLMs. True AI-First companies restructure around AI as the primary producer: development cycles shrink from weeks to a day, product managers are dismantled, and cross-team alignment is automated. Junior engineers adapt faster than seniors; the future rewards architecture + product + marketing generalists. The 'Agent Economy' means content may be produced for AI consumers. A 25-person team rebuilt their architecture in two weeks. Full transcript available.

x.com · 2 min · Agents · AI · Framework

05-28

Agent Unveiled: Principles, Architecture, and Engineering Practices

This article systematically examines the underlying architecture and engineering practices of agent systems. Starting from a stable agent loop, it contrasts workflows with agents, explains five control patterns, and emphasizes that the harness (evaluation baselines, execution boundaries, feedback, and fallbacks) often matters more than the model itself. It details context engineering via layered management and three compression strategies to prevent context rot, ACI‑oriented tool design, a four‑type memory system with consolidation, long‑task state externalization across sessions, protocol‑based multi‑agent coordination, eval frameworks (Pass@k and Pass^k), and event‑driven observability. Finally, it shows how these principles are implemented in OpenClaw, providing a practical reference for engineers building robust agents.

tw93.fun · 31 min · Agents · Framework · LLM

05-28

CSS Refactoring with an AI Safety Net

The author refactored a tangled CSS codebase into a clean architecture using Claude Code and Playwright, ensuring zero visual changes across seven phases. A Playwright script captured 9 app states, and after each phase, Claude compared screenshots to baseline, catching regressions like a line-height shift. The result: layered CSS with modern reset, unified button classes, and CSS variables. The post details state enumeration, script writing, and AI-driven diffing, and discusses trade-offs with dedicated tools. Essential reading for front-end developers tackling legacy CSS.

danielabaron.me · 12 min · AI · Framework

05-27

5 Agent Skill Design Patterns Every ADK Developer Should Know

With SKILL.md format standardised across 30+ agent tools, the real challenge is content design. This article distills five recurring patterns from ecosystem-wide practices: Tool Wrapper (on-demand library context), Generator (template fill-in for consistent output), Reviewer (checklist scoring by severity), Inversion (agent-led interview before acting), and Pipeline (strict multi-step with gate conditions). Each pattern includes working ADK code, helping developers build reliable agents.

x.com · 13 min · Agents · AI · Framework