Skip to content

Article Review: Group 23 — Kiro Steering, Cross-Tool Context Engineering, and Claude Code Productivity

Articles Reviewed

  1. Kiro Steering Documentation — kiro.dev/docs/steering/ (2026) — Official docs for Kiro's steering system: persistent markdown context files that define coding standards, project structure, and technology stack. Three foundational files (product.md, structure.md, tech.md), scoped inclusion via fileMatchPattern, global steering, and AGENTS.md support.

  2. "Teaching Kiro New Tricks with Agent Steering and MCP" — Kiro Blog (2026) — How steering files + MCP powers work together to give Kiro context about your project. Demonstrates the connection between persistent context (steering) and external tool access (MCP).

  3. "Claude Code Has 50+ Commands. Most Developers Use Only 5." — Rohan Mistry / Towards AI (Mar 2026) — Complete reference guide to Claude Code commands: slash commands (/init, /compact, /fork, /rewind, /btw), CLI flags, keyboard shortcuts. Claims developers mastering 15+ commands ship 3-4x faster.

  4. "The 10 Claude Plugins You Actually Need in 2026" — Rohan Mistry / Towards AI (Mar 2026) — Top 10 Claude plugins built on MCP: Feature-Dev (7-phase feature workflow), Frontend-Design (design instincts), Context7 (live docs), GitHub MCP, PostgreSQL MCP, Playwright, Brave Search, Google Workspace, Slack, Memory Bank.

  5. "Your AI Is Useless Without These 8 MCP Servers" — Usman Writes / Stackademic (Feb 2026) — 8 MCP servers for developer productivity: Vercel, Docker, Apify, Playwright, Ref (documentation), File System, Exa (semantic web search), and Supabase. Demonstrates the MCP pattern of connecting AI to external tools.

Kiro Steering vs Claude Code Context (Articles 1-2)

How Kiro and Claude Code Solve the Same Problem

Both tools solve session amnesia — teaching the AI about your project once instead of every conversation. They've converged on nearly identical patterns with different naming:

Concept Kiro Claude Code Nextpoint Architecture Repo
Persistent project context .kiro/steering/*.md CLAUDE.md + .claude/rules/ CLAUDE.md (master index, 300+ lines)
Foundational files product.md, structure.md, tech.md Single CLAUDE.md Single CLAUDE.md + principles/ directory
Scoped rules by file type fileMatchPattern in YAML front matter Rules can target file types rules/*.md loaded by category (manual)
Global (all projects) ~/.kiro/steering/ ~/.claude/ settings + memory ~/.claude/ settings + memory
Auto-learned context N/A MEMORY.md (auto-written by Claude) MEMORY.md index + topic files
Custom commands N/A (uses specs) .claude/commands/*.md 5 slash commands (check-boundaries, new-adr, etc.)
Skills N/A (uses powers) .claude/skills/ 3 skills (exploring-module, writing-reference-impl, reviewing-architecture)
MCP integration Powers (curated MCP + steering + hooks) mcp-servers in settings.json MCP configured in .claude/settings.json
Hooks (automation) Hooks on events Pre/PostToolUse hooks PreCommit (boundary check), PostToolUse (black formatting)
Enforcement Advisory (steering suggests) Advisory + hooks enforce Rules + hooks + pr-review (strongest enforcement)
Cross-project enforcement Global steering only Global settings only pr-review service injects rules per target repo
Spec-driven development Requirements.md -> Design.md -> Tasks.md Plan mode + ADRs ADRs + reference implementations
Agent definitions N/A .claude/agents/*.md N/A (pr-review is a service, not a Claude agent)
Cross-tool compatibility AGENTS.md support built-in Reads CLAUDE.md and AGENTS.md CLAUDE.md only

What Matters for Nextpoint (Uses Both Kiro and Claude Code)

Since the team uses BOTH tools, context files need to work for both:

CLAUDE.md is already compatible with Kiro. Kiro reads AGENTS.md (and by convention, CLAUDE.md-style files). The existing CLAUDE.md in this repo works for both tools without changes.

Kiro's three-file split is cleaner for large projects. Our CLAUDE.md is 300+ lines and growing. For developers using Kiro, the steering auto-generator would create product/structure/tech files from the project. These would complement (not replace) CLAUDE.md.

The scoped fileMatchPattern is a genuine improvement. Currently, all 15 rule files in rules/ are loaded by the Rule Index table in CLAUDE.md — developers manually consult the relevant rule. Kiro's approach of auto-loading rules based on which files you're editing is more efficient.

Recommendations for Cross-Tool Setup

For repos using both Kiro and Claude Code:

  1. Keep CLAUDE.md as the master — Both tools read it. It's the source of truth for project context.

  2. Let Kiro generate steering files — When a developer opens a Nextpoint repo in Kiro for the first time, let Kiro generate product.md, structure.md, tech.md from the project. These supplement CLAUDE.md with Kiro-optimized context.

  3. Don't duplicate rules — rules/ directory is for Claude Code. Kiro's steering files reference the same conventions but in Kiro's format. If a rule changes, update rules/ first (source of truth), then regenerate Kiro steering.

  4. Share hooks where possible — Both tools support pre-commit hooks. The hexagonal boundary check (core doesn't import from shell) should run regardless of which tool commits the code. Use git hooks (not tool-specific hooks) for enforcement that must be universal.

  5. AGENTS.md for cross-tool compatibility — Consider adding an AGENTS.md to repos that points to CLAUDE.md:

# AGENTS.md
See CLAUDE.md for project context, rules, and patterns.
This project follows the Nextpoint Architecture patterns
defined in the nextpoint-architecture repo.

Claude Code Commands and Productivity (Article 3)

Commands We Already Document vs New Ones to Consider

Our CLAUDE.md Session Hygiene section already covers: /btw, /fork, /rewind, --worktree, /clear, /compact. The article confirms these are the high-impact ones.

Commands worth adding to our documentation:

Command What It Does Nextpoint Use Case
/context Shows current context usage (% of window) Monitor during long architecture exploration sessions
/cost Shows token usage and cost for current session Track cost of pr-review agent sessions
/diff Compare current file changes Quick check before committing
/resume Continue most recent task Resume after /compact or disconnect
/todos Show/manage task list Track multi-step architecture reviews

Context Budget Insight

The article claims developers mastering 15+ commands ship 3-4x faster. The real insight is context budget management. The commands that matter most are the ones that manage context: /compact, /btw, /fork, /context.

Our CLAUDE.md already has a "Context Budget Management" section. The article validates this approach — context is the bottleneck, not capability.

MCP and Plugin Ecosystem (Articles 4-5)

Plugins/MCPs Already Relevant to Nextpoint

Plugin/MCP Relevance Status
Context7 Live library docs (prevents hallucinated APIs) Already configured in this session
PostgreSQL MCP Direct DB queries from Claude/Kiro Useful for exploring per-case databases during development
Docker MCP Container debugging ("why does this fail in CI but not locally?") Useful for ECS Fargate debugging (documentuploader, documentextractor)
Playwright MCP Browser automation for testing Potentially useful for Rails frontend testing
File System MCP Project-wide code understanding Built into Claude Code already
GitHub MCP PR and issue management Nextpoint uses Bitbucket, not GitHub. Limited use.
Feature-Dev 7-phase feature development workflow Worth evaluating for documentsearch prototype build

MCP Pattern for Nextpoint Development

The consistent message across both MCP articles: the value isn't any single MCP server — it's the pattern of connecting the AI to your actual tools and data sources. For Nextpoint development, the highest-impact MCPs would be:

  1. Bitbucket MCP (if one exists) — PR management, code review from within Claude Code/Kiro
  2. AWS MCP — CloudWatch logs, Lambda debugging, SQS queue inspection directly from the IDE
  3. PostgreSQL/MySQL MCP — Query per-case databases during development
  4. Elasticsearch MCP — Inspect ES indices and mappings during documentsearch development

The AWS Observability Power for Kiro (CloudWatch + Application Signals + CloudTrail + AWS Docs) is particularly relevant — it would let Kiro help debug Lambda issues by reading CloudWatch logs directly.

Cross-Article Synthesis

The Convergence

All five articles point to the same architectural shift: persistent context + external tool access = effective AI-assisted development. Kiro calls it "steering + powers." Claude Code calls it "CLAUDE.md + MCP." The pattern is identical:

Persistent context files (what the AI knows about your project)
  + Scoped rules (what the AI should enforce)
  + External tool access (what the AI can interact with)
  + Hooks (what happens automatically)
  = AI that works WITH your codebase, not just IN it

Nextpoint's architecture repo is already this pattern — implemented before either Kiro or Claude Code formalized it. The CLAUDE.md + rules/ + .claude/commands/ + .claude/skills/ + .claude/settings.json (hooks + MCP) structure predates Kiro's steering model but matches it conceptually.

What Nextpoint Has That Neither Tool Provides Natively

Cross-repository architectural enforcement. The pr-review service reads this architecture repo and injects relevant rules into PR review agents based on the target repository. Neither Kiro nor Claude Code can enforce patterns across repositories — they work within a single project. The architecture repo + pr-review combination is a unique capability.

What's Worth Adopting

From Idea Priority Effort
Kiro fileMatchPattern for scoped rule loading Medium Add front matter to rules/ files
Kiro AGENTS.md in repos for cross-tool compatibility Low One-line file pointing to CLAUDE.md
Kiro Auto-generate steering from project scan Low Let Kiro generate its files; don't maintain manually
Claude Code /context monitoring during long sessions Medium Add to Session Hygiene section
MCP ecosystem AWS Observability Power for Kiro Medium Install when developing documentsearch
MCP ecosystem PostgreSQL/MySQL MCP for DB access Medium Useful for per-case DB exploration

Action Items

  1. Add AGENTS.md to Nextpoint repos — one-line pointer to CLAUDE.md for Kiro compatibility. No maintenance overhead.
  2. Evaluate fileMatchPattern — could our rules/ files use front matter to auto-load based on file being edited? Would reduce context noise.
  3. Document cross-tool setup — add a section to CLAUDE.md explaining how Kiro and Claude Code coexist on the same repo.
  4. Install AWS Observability Power — when building documentsearch, the CloudWatch MCP would help debug Lambda issues directly from Kiro.
Ask the Architecture ×

Ask questions about Nextpoint architecture, patterns, rules, or any module. Powered by Claude Opus 4.6.