惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Engineering at Meta
Engineering at Meta
T
Threatpost
P
Palo Alto Networks Blog
NISL@THU
NISL@THU
O
OpenAI News
Project Zero
Project Zero
G
GRAHAM CLULEY
P
Privacy International News Feed
A
Arctic Wolf
Microsoft Azure Blog
Microsoft Azure Blog
H
Help Net Security
M
MIT News - Artificial intelligence
T
Threat Research - Cisco Blogs
S
Security @ Cisco Blogs
Google DeepMind News
Google DeepMind News
B
Blog RSS Feed
D
Docker
aimingoo的专栏
aimingoo的专栏
博客园 - 【当耐特】
N
Netflix TechBlog - Medium
云风的 BLOG
云风的 BLOG
雷峰网
雷峰网
W
WeLiveSecurity
P
Proofpoint News Feed
腾讯CDC
Cloudbric
Cloudbric
S
Secure Thoughts
C
Check Point Blog
博客园 - Franky
T
The Exploit Database - CXSecurity.com
T
Troy Hunt's Blog
GbyAI
GbyAI
Security Archives - TechRepublic
Security Archives - TechRepublic
Application and Cybersecurity Blog
Application and Cybersecurity Blog
月光博客
月光博客
C
Cyber Attacks, Cyber Crime and Cyber Security
I
Intezer
TaoSecurity Blog
TaoSecurity Blog
L
Lohrmann on Cybersecurity
V
Visual Studio Blog
F
Fortinet All Blogs
博客园 - 叶小钗
C
CXSECURITY Database RSS Feed - CXSecurity.com
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
Recorded Future
Recorded Future
C
Cisco Blogs
博客园 - 司徒正美
Stack Overflow Blog
Stack Overflow Blog
Y
Y Combinator Blog
Apple Machine Learning Research
Apple Machine Learning Research

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
CLAUDE.md for Astro: 13 Rules That Stop AI from Shipping Too Much JavaScript
Olivia Craft · 2026-05-27 · via DEV Community

Astro is built around one idea: ship less JavaScript. Islands architecture means only the interactive components hydrate on the client. Everything else is static HTML. It's a framework with strong opinions about what belongs on the server and what belongs on the client.

AI tools don't know those opinions. They know Astro exists. They don't know you're using Astro 4 or 5, whether you're using SSR or static output, which UI framework you've wired up for islands (React, Vue, Svelte, or none), or that adding client:load to every component defeats the entire purpose of using Astro.

The result: generated Astro code that technically works but sends megabytes of JavaScript to the browser, misuses the content collections API, puts server-only code in client components, and generates React patterns in .astro files.

A CLAUDE.md file locks in the context that makes Astro-specific AI generation correct. Here are 13 rules that fix the most common mistakes.


Rule 1: Declare your Astro version, output mode, and UI framework

## Stack
- Astro: 5.x (NOT 4.x — content layer API, server islands, and routing differ)
- Output: static (NOT server/hybrid — no SSR unless explicitly noted)
- UI framework for islands: React 18 (used ONLY for interactive components)
- Styling: Tailwind CSS 4.x
- Node: 22 LTS

Enter fullscreen mode Exit fullscreen mode

Astro 4 and 5 have different content layer APIs. Static and SSR output modes have completely different rules about what code can run where. The UI framework determines island syntax. Every one of these changes the generated code.


Rule 2: .astro files are server-first — no browser APIs at the top level

## Astro Component Model
The frontmatter section of .astro files (between ---) runs on the SERVER only.
NEVER use browser APIs (window, document, localStorage, fetch with credentials)
in .astro frontmatter.

// CORRECT — server-side in frontmatter
---
const posts = await getCollection('blog');
const data = await fetch('https://api.example.com/data').then(r => r.json());
---

// WRONG — browser API in frontmatter (throws at build time)
---
const saved = localStorage.getItem('theme'); // window is undefined on server
---

Enter fullscreen mode Exit fullscreen mode

Claude frequently puts localStorage, window, and document in .astro frontmatter. These throw at build time in static mode and at request time in SSR. The error messages are cryptic.


Rule 3: Use client: directives intentionally — not by default

## Islands Architecture
Interactive components MUST declare a hydration directive explicitly.
Do NOT add client:load to every component — this defeats Astro's performance model.

Choose the right directive:
- client:load   → hydrate immediately (use for above-the-fold critical UI only)
- client:idle   → hydrate when browser is idle (most interactive components)
- client:visible → hydrate when component enters viewport (below-fold content)
- client:only   → skip SSR entirely (use only when component CANNOT run on server)

// CORRECT
<SearchBar client:idle />
<NewsletterForm client:visible />
<VideoPlayer client:only="react" />

// WRONG — hydrating everything immediately
<Header client:load />
<Footer client:load />
<Sidebar client:load />

Enter fullscreen mode Exit fullscreen mode

The most common Astro mistake: adding client:load everywhere because Claude doesn't know the performance intent. Specify which directive to use as default for new interactive components.


Rule 4: Content Collections for all structured content

## Content Management
ALL blog posts, documentation, case studies, and structured content MUST use
Astro Content Collections defined in src/content/config.ts.
Never import markdown files with raw import statements.
Never store content as hardcoded arrays in .astro files.

// CORRECT — src/content/config.ts
import { defineCollection, z } from 'astro:content';
export const collections = {
  blog: defineCollection({
    type: 'content',
    schema: z.object({
      title: z.string(),
      pubDate: z.date(),
      tags: z.array(z.string()),
    }),
  }),
};

// In page
const posts = await getCollection('blog');

// WRONG
import post from '../content/post.md'; // raw import bypasses collection

Enter fullscreen mode Exit fullscreen mode

Claude generates raw markdown imports and hardcoded content arrays in pages. Content Collections provide type safety, schema validation, and the correct Astro API for structured content.


Rule 5: Image optimization through Astro's Image component

## Images
ALL images MUST use Astro's built-in <Image> or <Picture> component.
Never use raw <img> tags for content images.
Images in src/assets/ are optimized at build time.
External images require explicit width and height props.

// CORRECT
import { Image } from 'astro:assets';
import heroImage from '../assets/hero.jpg';

<Image src={heroImage} alt="Hero" />
<Image src="https://example.com/img.jpg" alt="External" width={800} height={600} />

// WRONG
<img src="/images/hero.jpg" alt="Hero" />  // no optimization

Enter fullscreen mode Exit fullscreen mode

Claude generates raw <img> tags. In Astro, this bypasses the image optimization pipeline and fails TypeScript checks when strict mode is on.


Rule 6: Styles are scoped by default — global styles require explicit opt-in

## CSS Scoping
Styles in <style> blocks inside .astro files are SCOPED to that component by default.
To apply global styles, use <style is:global> or import from a CSS file.
NEVER use :global() selector for component-specific styles — it leaks into the page.

// CORRECT — scoped (default)
<style>
  .card { border-radius: 8px; }  // only applies to this component's .card
</style>

// CORRECT — intentionally global
<style is:global>
  :root { --color-primary: #3b82f6; }
</style>

// WRONG — global override for a local component concern
<style>
  :global(.card) { border-radius: 8px; }  // leaks everywhere
</style>

Enter fullscreen mode Exit fullscreen mode

Claude generates :global() wrappers when it encounters styling issues. This is almost always wrong — it means the style wasn't properly scoped to begin with.


Rule 7: API routes are TypeScript files in src/pages/api/

## API Routes
Server-side API endpoints go in src/pages/api/ as .ts files.
They export a named function for each HTTP method.
API routes only work in SSR mode (output: 'server' or 'hybrid').
In static output mode, API routes are NOT available — use edge functions or external APIs.

// CORRECT — src/pages/api/subscribe.ts (SSR mode only)
import type { APIRoute } from 'astro';

export const POST: APIRoute = async ({ request }) => {
  const body = await request.json();
  // process...
  return new Response(JSON.stringify({ success: true }), {
    headers: { 'Content-Type': 'application/json' },
  });
};

Enter fullscreen mode Exit fullscreen mode

Claude generates API routes without checking the output mode. In static mode, they silently don't work. Specify your output mode so Claude knows whether API routes are available.


Rule 8: Environment variables — server vs client

## Environment Variables
Server-only secrets: use import.meta.env.SECRET_KEY (never exposed to client)
Client-safe variables: must be prefixed PUBLIC_ (e.g., PUBLIC_SITE_URL)
NEVER use process.env in Astro — it doesn't work in all environments.

// CORRECT
const apiKey = import.meta.env.SECRET_API_KEY;     // server only
const siteUrl = import.meta.env.PUBLIC_SITE_URL;   // safe for client

// WRONG
const apiKey = process.env.SECRET_API_KEY;          // may be undefined in Astro

Enter fullscreen mode Exit fullscreen mode

Claude uses process.env out of habit from Node.js projects. Astro's env handling is different and the public/private distinction is enforced by the PUBLIC_ prefix convention.


Rule 9: Dynamic routes use getStaticPaths for static output

## Dynamic Routes
Static output pages with URL parameters MUST export getStaticPaths() to define
all valid paths at build time.
In SSR mode, getStaticPaths is not required (routes are resolved at runtime).

// CORRECT — static output dynamic route
export async function getStaticPaths() {
  const posts = await getCollection('blog');
  return posts.map(post => ({
    params: { slug: post.slug },
    props: { post },
  }));
}

Enter fullscreen mode Exit fullscreen mode

Without getStaticPaths, dynamic routes in static output mode produce a build error. Claude often omits it when generating page files.


Rule 10: Layouts handle document structure — components don't

## Layout Convention
The <html>, <head>, and <body> tags belong in layout files (src/layouts/).
Page .astro files use a layout component for document structure.
Component .astro files NEVER render <html>, <head>, or <body>.

// CORRECT — src/layouts/BaseLayout.astro
---
const { title } = Astro.props;
---
<!DOCTYPE html>
<html lang="en">
  <head><title>{title}</title></head>
  <body><slot /></body>
</html>

// Page uses layout
---
import BaseLayout from '../layouts/BaseLayout.astro';
---
<BaseLayout title="Home">
  <h1>Welcome</h1>
</BaseLayout>

Enter fullscreen mode Exit fullscreen mode

Claude sometimes generates full HTML documents in component files. Establishing the layout pattern prevents this.


Rule 11: TypeScript strict mode — no implicit any

## TypeScript
This project uses TypeScript strict mode (tsconfig: astro/tsconfigs/strict).
No implicit any. No type assertions without justification.
Astro component props MUST be typed with Props interface.

// CORRECT
interface Props {
  title: string;
  description?: string;
  pubDate: Date;
}
const { title, description, pubDate } = Astro.props;

// WRONG
const { title, description, pubDate } = Astro.props; // untyped in strict mode

Enter fullscreen mode Exit fullscreen mode


Rule 12: Prefer Astro components over framework components for static UI

## Component Choice
Use .astro components for all static or server-rendered UI.
Use React/Vue/Svelte components ONLY when the component needs client-side
interactivity (state, event handlers, browser APIs).
A component that only displays data and has no event handlers should be .astro.

// CORRECT — static card with no interactivity → .astro component
// CORRECT — search with onChange handler → React component with client:idle
// WRONG — React component with no state/events → use .astro instead

Enter fullscreen mode Exit fullscreen mode

Claude defaults to React for everything when a React integration is detected. Specify this rule to keep the bundle small.


Rule 13: Build output verification commands

## Build and Preview
Use these commands for development and verification:
- npm run dev       → development server (localhost:4321)
- npm run build     → production build (output to dist/)
- npm run preview   → preview production build locally

For checking bundle size: npx astro build && ls -la dist/

TypeScript check without building: npx astro check

Enter fullscreen mode Exit fullscreen mode

Without this rule, Claude generates npm start or npm run serve commands that don't exist in Astro projects.


Putting it together

Astro's performance model is intentional: static by default, interactive only where needed, server code stays on the server. AI tools don't know which components you intend to be interactive, which environment variables are safe for the client, or that client:load on every component undoes the framework's core value proposition.

A CLAUDE.md that declares your output mode, your island hydration defaults, your content collection schema, and your component choice rules gives Claude the context to generate Astro code that ships less JavaScript — which is the whole point.

If you're using Claude Code or Cursor for an Astro project, the full CLAUDE.md template — covering 26 other frameworks — is in the CLAUDE.md Rules Pack.

oliviacraftlat.gumroad.com/l/skdgt — $27, instant download