Signing you in...

Please wait while we verify your authentication

Article · Friday, May 15, 2026

Agentic Coding

Top tech stories today across software, hardware, AI, and product launches. Senior engineer audience — skip rumour churn and pre-announcement leaks. Lead with shipping-now stories and what changed for builders.

By Marius BongartsTech9 editions
← See today's latest
Editions8 / 9
Generated by AI overnight from public sources, refreshed daily.
Agentic Coding
Friday, May 15, 2026
AI Agents - Agentic Coding

Skills repos drop, vibe coding gets a security playbook, and alignment drills land

1 min read

Vercel Skills CLI

Your agent skills just became portable.

Vercel Labs shipped an open CLI that installs and manages reusable instruction sets across 51+ coding agents, including Claude Code and Cursor [Source: GitHub]. Each skill lives in a SKILL.md file with YAML frontmatter, and you can scope them globally or per-project. The tool handles discovery, templates, and cross-agent compatibility out of the box. Run npx skills to browse what's available and start composing your own.

Reusable prompts finally have a package manager.

Matt Pocock's Skills

Closing the gap between what you meant and what the agent built.

Matt Pocock's new skills repo targets a specific failure mode: the agent understands your words but misses your intent [Source: GitHub]. His /grill-me and /grill-with-docs skills force a grilling session before coding starts, surfacing misalignments early. Other composable skills cover TDD loops, structured debugging, and architecture drift prevention. The collection pairs well with the CONTEXT.md pattern for shared domain language.

Worth cloning if your agents keep solving the wrong problem.

Vibe coding security

Most vibe coding failures happen at deploy, not in the code.

A new guide lays out a five-layer security stack for solo builders: secrets in environment variables, microVM sandboxing instead of plain containers, least-privilege database credentials, isolated preview environments per PR, and human review before shipping [Source: Northflank]. The author recommends prompting for security constraints explicitly—input validation, parameterized queries, no hardcoded secrets—to raise the baseline of generated code. Platforms like Northflank apply these defaults automatically.

Add the prompt suffix now; thank yourself later.

Vibe coding workflow

You don't write code—you talk and audit.

A practical breakdown confirms the emerging four-tool stack: conversational AI for initial sketches, an AI editor like Cursor for iteration, GitHub for version control, and a one-click deploy service [Source: DEV]. Human judgment stays critical at three points—crafting specific prompts, catching subtle bugs the model misses (especially auth and database issues), and making scope calls. The process is collaborative, not hands-off.

Audit harder than you prompt.

Sources
mattpocock/skills: Skills for Real Engineers. Straight from ... - GitHub
mattpocock/skills: Skills for Real Engineers. Straight from ... - GitHub
16 hours ago ... I built these skills as a way to fix common failure modes I see with Claude Code, Codex, and other coding agents. #1: The Agent Didn't Do What I Want. "No-one ...
github.com
AI Summary

Matt Pocock's skills repository provides advanced agent engineering practices for Claude Code and Cursor users building production applications. The collection emphasizes alignment through grilling sessions (/grill-me and /grill-with-docs) to close communication gaps between developer intent and agent output, and introduces shared domain language via CONTEXT.md files to reduce verbosity and improve token efficiency. Key skills address common failure modes: /grill-with-docs combines requirement clarification with Architecture Decision Records, /tdd implements red-green-refactor loops for reliable code feedback, /diagnose provides structured debugging workflows, and /improve-codebase-architecture prevents complexity drift—all composable tools designed for real engineering rather than exploratory "vibe coding" and suitable for SaaS development workflows.

Visit source
Vibe Coding, Demystified - DEV Community
Vibe Coding, Demystified - DEV Community
9 hours ago ... Others use it just for the rough draft. AI-powered Editor: This is where the code gets edited with help from an assistant that can see all the files at once.
dev.to
AI Summary

Vibe coding is a collaborative approach to software development where developers use AI tools in plain English conversation rather than writing code manually. The practical workflow involves four key tools: a conversational AI (like Claude or ChatGPT) for initial sketches, an AI-powered editor (like Cursor) for iterative development, GitHub for version control, and a deployment service (Cloudflare Pages, Vercel, or Netlify) for going live. Human judgment remains critical at three stages: crafting specific initial prompts, auditing the AI's output for subtle errors (especially security issues), and making scope and quality decisions. The article emphasizes that beginners don't need prior coding knowledge but benefit from being specific about requirements and patient with follow-up iterations. Real-world barriers like authentication bugs or database vulnerabilities require human review, making the process fundamentally collaborative rather than fully automated.

Visit source
vercel-labs/skills: The open agent skills tool - npx skills - GitHub
vercel-labs/skills: The open agent skills tool - npx skills - GitHub
10 hours ago ... ... Best Practices" # Install to specific agents npx skills add vercel-labs/agent-skills -a claude-code -a opencode # Non-interactive installation (CI/CD ...
github.com
AI Summary

The website content provides a comprehensive CLI tool for managing agent skills across 51+ coding agents including Claude Code and Cursor. It documents how to install, create, and manage reusable instruction sets (skills) that extend AI coding agents' capabilities, such as generating release notes, creating PRs, and integrating with external tools. The skills are defined in SKILL.md files with YAML frontmatter and can be installed at project or global scope. The tool supports skill discovery, creation templates, and compatibility across different agents, directly addressing the user's interest in efficient workflows with Agent Skills and best practices for working with Claude Code and Cursor.

Visit source
How to vibe code securely in 2026 | Blog - Northflank
How to vibe code securely in 2026 | Blog - Northflank
10 hours ago ... Vibe coding security guide for individual builders: how to keep secrets out of ... For vibe-coded apps that include AI coding assistant features, code ...
northflank.com
AI Summary

The article provides best practices for secure vibe coding workflows, which directly aligns with your interest in advanced AI assistant coding techniques. It emphasizes a five-layer security approach: keeping secrets out of code through environment variables and secrets managers, sandboxing code execution using microVM isolation (Kata Containers, Firecracker, gVisor) rather than standard containers, scoping database credentials to least-privilege access, isolating development and production environments with preview environments per pull request, and reviewing AI-generated output before deployment. The guide stresses that most vibe coding security failures occur at the deployment layer rather than the code layer, and recommends requesting security constraints explicitly in prompts ("Generate this with input validation, parameterised queries, least-privilege access, secure secret handling, and no hardcoded credentials") to improve the baseline of generated code. For solo founders using tools like Claude and Cursor, the article notes that deployment platforms like Northflank can apply these controls by default without requiring infrastructure expertise, allowing you to focus on rapid iteration while maintaining production-grade security.

Visit source
Compiled overnight by MorningMail.aiDelivered at 04:55 AM