682: Medium Core
https://atp.fm/682
MacBook Neo details, Studio Display XDR tech and impressions, Marco tries a Garmin, and Casey tries to watch F1.
682: Medium Core
https://atp.fm/682
MacBook Neo details, Studio Display XDR tech and impressions, Marco tries a Garmin, and Casey tries to watch F1.
@marcobarrios You can create skill files relevant to the specific strategy, development practices, or architecture of the project. They do not pollute the context window because only the YAML frontmatter is exposed to the agent. Only if the task is relevant will the agent load the skill information. This can be very powerful when chained together and combined with tool use. For example, coder > reviewer skill using linting/Playwright > feedback back to coder in a loop.
https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview
@atpfm @siracusa I’m a huge proponent of your work, but your view on AI is a rooted in a standard chat interface. Agent orchestration is here, with teams of agents with specialized skills swarming on an issue. One assistant can make dumb mistakes, but a *team* with a reviewer recognizes issues and iterates until all issues are resolved. Be prepared for your relationship with coding to change this year.
Source: I’m a senior AI engineer working at a midsize bank.