Why Symlinking Cursor and Claude Code Rules Breaks Silently and How to Fix It

·6 views

Developers using both Cursor and Claude Code AI tools on the same repository often attempt to share a single rules directory via symlink, but this approach fails in two distinct ways. Cursor only reads files with a .mdc extension while Claude Code reads .md files, meaning a shared directory will cause one tool to silently ignore all rules. The two tools also use different YAML frontmatter keys for scoping — Cursor uses globs and alwaysApply, while Claude Code uses a paths list — so a file written for one format is misread by the other without any error or warning. A proposed solution treats Claude Code's .md files as the single source of truth and uses a small, dependency-free Node.js script to automatically generate correctly formatted .mdc files for Cursor. This code-generation approach keeps both tools in sync from one canonical set of rules, eliminating the silent misconfiguration that symlinks introduce.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How Terraform Can Replace Click-Ops Chaos in Dashboard and Alert Management

Engineering teams managing observability through manual UI clicks accumulate 'click-ops debt,' resulting in broken, unowned, and outdated dashboards that are hard to audit or maintain. The article proposes storing all dashboards, alerts, and SLO definitions as code in Git repositories using infrastructure-as-code tools like Terraform, alongside the services they monitor. Supported providers include Datadog, Grafana, Prometheus via ArgoCD, and New Relic, with each team advised to pick a single source of truth. A reusable Terraform module can generate a full observability stack — dashboards, alerts, SLOs, and escalation policies — from a single service-level call. The recommended approach distinguishes between core observability defined in code and exploratory custom dashboards left to the UI, with a phased migration starting from one service in the first week.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Tokyo Developer Builds Vue 3 npm Package for Japanese Postal Code Lookups

A full-stack engineer based in Tokyo created and published an open-source npm package called nihonpost after failing to find a suitable library for Japanese postal code address auto-fill. Existing packages on npm lacked TypeScript support, proper documentation, or Vue 3 compatibility. The package is built TypeScript-first, includes a Vue 3 composable, and requires no third-party API — instead, users self-host postal data split into prefix-based JSON chunks that are fetched on demand and cached. A single configuration call at startup is all that is needed before the lookup function can resolve a postal code into prefecture, city, and town fields. The package is now publicly available on npm, and the developer is welcoming issues and pull requests from the community.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Seven-Point Mini-Audit Template Helps AI-Built Launch Pages Win Visitor Trust

A developer has published a lightweight audit framework designed to help small AI-built apps and launch pages address common trust barriers before driving traffic. The seven-check template evaluates key elements including clarity of purpose, call-to-action visibility, social proof, mobile presentation, and the free-to-paid conversion path. Rather than producing lengthy strategy documents, the framework outputs a short ranked list of specific fixes prioritized by impact. The author recommends starting with a single public URL and asking what a first-time visitor is most likely to misunderstand. Sample mini-audits, a free offline scorecard, and a checklist library have been made available through Payhip and Gumroad.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Structured, Field-Based Prompt Workflow Helps Debug AI Image Generation

A developer-focused workflow for AI image prompting breaks prompts into discrete fields — subject, layout, material, light, mood, and use case — rather than using single long requests. The approach draws on software testing principles: changing only one variable at a time makes it easier to identify which element caused an unwanted output. Starting with a visual reference image instead of a written sentence provides a concrete baseline before any prompt is written. Tools that display example images alongside their prompts, such as Timi AI, can serve as structured starting points that users adapt rather than copy directly. The method also improves team collaboration, allowing designers, developers, and marketers to each engage with a specific, inspectable part of the prompt.

0 comments Read more at DEV Community