DROPGoogle launches Gemini 3.8 Flash TTS and Flash-Lite TTS///DROPGemini Omni brings 1080p generation to Google Vids///BREAKClaude Opus 5.5 is here: 1M context, $4 input / $20 output///BREAKOpenAI adds GPT-6 Sol and Luna to the GPT-6 family///PAPEROpus 5.5's system card documents gains—and evaluation limits///BREAKGrok 4.7 launches at $2 input / $6 output per million tokens///DROPGrok Voice Transcribe 2.0 targets difficult real-world audio///TRENDGoogle steers new Gemini API projects to 3.8 Flash or 3.5 Flash-Lite///DROPGoogle launches Gemini 3.8 Flash TTS and Flash-Lite TTS///DROPGemini Omni brings 1080p generation to Google Vids///BREAKClaude Opus 5.5 is here: 1M context, $4 input / $20 output///BREAKOpenAI adds GPT-6 Sol and Luna to the GPT-6 family///PAPEROpus 5.5's system card documents gains—and evaluation limits///BREAKGrok 4.7 launches at $2 input / $6 output per million tokens///DROPGrok Voice Transcribe 2.0 targets difficult real-world audio///TRENDGoogle steers new Gemini API projects to 3.8 Flash or 3.5 Flash-Lite///
DARC.DEV
All guides
WorkflowLevel · Build#Claude Code#Coding#Opus 5.5

A maintainable Claude Code workflow after the Opus 5.5 release

Repository instructions, planning gates and reviewable diffs—plus the model settings that now need a fresh check.

DCDariusz Czechowicz23 Sept 20263 min readPractical guide
50
Workflow
Source-checked Sources & corrections
2 practical sections · checklist · sources

Practical guide. Provider claims are attributed to the sources below. This page does not claim a new independent DARC benchmark.

For: Developers and teams putting AI into practical use

⚡ TL;DR — the 30-second version

  • Keep repository instructions short and executable.
  • Review Opus 5.5's changed reasoning and context requirements.
  • Inspect tests and diffs before approving changes.

Keep project instructions focused on the repository map, conventions, runnable checks and approval boundaries. Avoid instructions that depend on a model alias silently continuing to point at the same version.

With Opus 5.5, review the request and thinking behavior, cache economics and preserved-context constraints in the current documentation. A code assistant can be available in multiple products while still having surface-specific options and usage limits.

“Write repository instructions like an onboarding document: useful boundaries, tested commands and where the sharp edges are.”
— Editorial interpretation

Use a plan-review-execute loop for changes that cross architectural boundaries. Ask for focused diffs and independent tests. For repeated workflows, keep commands and checklists in version control so another developer can reproduce the process.

Record the model and harness used when evaluating a workflow change. This is a practical setup guide, not a claim of a measured daily productivity gain or a released set of personal dotfiles.

Field guide / 01

Keep project context executable

A useful CLAUDE.md describes the repository map, build commands, conventions and dangerous assumptions. Verify every command it recommends. Stale instructions can repeatedly send the agent down a broken path.

Separate instructions from enforcement. The current configuration docs place permissions in settings, while hooks observe or influence lifecycle events. A best-effort hook condition must not become your only hard security boundary.

Field guide / 02

Review proof rather than a confident summary

Ask for the exact tests executed, the files changed and remaining uncertainty. Compare that summary with the trace and diff. Review any changed test assertions independently of the implementation.

For repeated work, keep a small regression set and an explicit model/harness record. Update it after installing plugins or adding MCP servers because the tool surface has changed even if the task prompt has not.

Before you ship

0/5

Use this as a review aid. Checks reset when you leave this page.

Questions that come up

Should I put all team knowledge in one huge instruction file?

No. Keep core instructions focused and load task-specific material deliberately. Unrelated or contradictory context can increase cost and reduce clarity.

Put it into practiceInspect the Claude Code profile

Sources & verification

Last checked 23 Sept 2026. Publication dates and access conditions belong to the linked originals.

  1. 01Introducing Claude Opus 5.5Anthropic↗
  2. 02Claude Platform release notesAnthropic↗
  3. 03Claude Code — commands and workflowsAnthropic↗
  4. 04Claude Code — permission and configuration referenceAnthropic↗
  5. 05Claude Code — hook lifecycle and limitationsAnthropic↗
Editorial policy and correction log →
#Claude Code#Coding#Opus 5.5