Imported from smmariquit/tools (AGENTS.md). Install upstream with npx skills add smmariquit/tools. Copyright stays with the author.

<!, BEGIN:nextjs-agent-rules, >

This is NOT the Next.js you know

This version has breaking changes: APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ before writing any code. Heed deprecation notices. <!, END:nextjs-agent-rules, >

<!, BEGIN:i18n-agent-rules, >

Internationalization (i18n) & Translation

Every time you create or modify a UI component (like a calculator in src/app/[locale]/), you MUST ensure that all user-facing text is translated using next-intl.

1. Never hardcode English text in the JSX.
2. Use useTranslations (for Client Components) or getTranslations (for Server Components).
3. Add the extracted English strings to messages/en.json.
4. Translate the strings into conversational Taglish (Tagalog + English) following CONVERSATIONAL_GUIDE.md and add them to messages/tl.json.
5. Make sure your translation namespaces match the component name (e.g., SalaryCalculator, IncomeTaxCalculator). <!, END:i18n-agent-rules, >

<!, BEGIN:tools-agent-rules, >

Cross-Linking Tools

Whenever you create or update a tool, you MUST include a "Related Tools" section at the bottom of the tool's interface (or blog post). This section should contain links to exactly 3 other tools on the platform that are contextually relevant (e.g., if it's the Salary Calculator, link to the 13th Month Pay, Income Tax, and Freelance Tax calculators). <!, END:tools-agent-rules, >

<!, BEGIN:a11y-agent-rules, >

Accessibility & Keyboard Navigation

We aim to ensure that our platform is highly accessible. Every time you create or modify a UI component:

1. Ensure all interactive elements (buttons, inputs, links) are easily focusable via Tab.
2. Do NOT break keyboard navigation. Support keyboard shortcuts where logical (e.g. Enter to submit, Esc to close modals).
3. Ensure sufficient color contrast and appropriate aria-labels for screen readers. <!, END:a11y-agent-rules, >

<!, BEGIN:mdx-changelog-rules, >

MDX content: visuals, sources, edited date + changelog (mandatory, no exceptions)

Whenever you create or edit ANY file under src/content/blog/**/*.mdx, regardless of the task or which agent is doing it, you MUST:

1. Visuals where applicable: add relevant charts/graphs/images when they aid understanding. Use <MdxChart.../> for data viz (bar/line/area/pie) and standard markdown images for diagrams/screenshots. Do not force visuals onto purely conceptual articles. 1b. Authority signal where credible: where genuinely warranted, embed a real authority's explainer with <YouTube id="..." title="..."/>, recommend a real book with a personal aside, or link a complementary tool with a short kudos note. Verified, real items only (research/deep-research-authority-prompt.md); never fabricate a video ID/ISBN/channel. Don't force one onto every article.
2. Sources, ALWAYS: end every writeup with a ## Sources section listing the primary references used, as live links (verify each returns HTTP 200). It sits just above ## Changelog.
3. Set updatedAt: "YYYY-MM-DD" in the frontmatter to today's date (keep the original date: unchanged).
4. Prepend a one-line dated entry (newest first) to the ## Changelog section, kept as the LAST section. Never delete past entries. Use ## Changelog (h2), not ### (which becomes FAQ schema).

Canonical bottom-of-file order: Related Tools list, then ## Sources, then ## Changelog.

Full spec and examples: .cursor/rules/mdx-editing.mdc. <!, END:mdx-changelog-rules, >