rhino-inquisitor-com

Technical SEO strategy for rhino-inquisitor.com — URL preservation, redirect architecture, canonical signals, structured data, sitemap/robots policy, and Search Console workflow. Use when making decisions about URL disposition (keep/merge/retire), redirect implementation, canonical tags, sitemap/robots.txt policy, JSON-LD schema, or Google Search Console actions.

Bonsai-backed official documentation and web research workflow. Use before technical changes that depend on platform behavior, when fetching documentation or web pages, when listing/pruning the local research cache, or when importing manually gathered notes.

Hugo SSG configuration, templates, partials, front matter, URL/route management, and GitHub Pages deployment for rhino-inquisitor.com. Use when writing hugo.toml, src/layouts, src/partials, src/archetypes, or GitHub Pages deployment workflows, and when debugging Hugo build, routing, or output behaviour.

Creates and fills implementation ticket documents for tracking tasks, outcomes, and progress without Jira. Use when asked to "create a ticket", "write an implementation ticket", "track a task", "describe a work item", or "log what needs to be done". Generates structured markdown tickets with goals, acceptance criteria, and a task checklist.

Guides documentation updates for new or changed features, workflows, and governance. Use when adding, changing, or deprecating behavior that users or maintainers must understand.

Guidance for writing, rewriting, or removing image captions using the RHI-094 cleanup standards. Use when reviewing img-caption shortcode content, figure captions, and nearby post-figure paragraphs for redundancy and reader value.

Edit sentence-level prose to remove formulaic AI patterns and replace them with direct, specific, human writing. Use when refining markdown posts in src/content/posts/** after the structure and technical claims are already sound.

Shape technical posts so hands-on implementers and solution-level readers get the context they need without splitting the draft into two competing tracks. Use when a post must explain both how something works and why the design choice matters.

Write technical explanations that stay correct while remaining readable for readers who are still learning the subject. Use when drafting or revising teaching-oriented posts, especially SFCC and platform-specific explainers.

Guidance for using Chrome DevTools MCP to inspect live Chrome pages, debug browser behavior, run performance traces, and capture screenshots. Use when a task needs browser automation, DOM and CSS inspection, console or network debugging, or page-performance analysis.

Write code examples and walkthroughs that teach one technical idea at a time and explain why each step matters. Use when authoring or revising code-heavy posts in src/content/posts/**.

Use when writing, reviewing, or refactoring CSS in plain stylesheets, Hugo templates, component markup, CSS Modules, or Tailwind-enabled projects. This skill maps browser targets to safe modern CSS features so native layout, theming, and animation primitives replace legacy workarounds when support allows.

Use when designing or implementing motion for web interfaces, including CSS transitions and keyframes, `linear()` easing design, transform strategy (`translate`/`rotate` vs `transform`/`translate3d()`), and deep View Transitions API patterns for route and state continuity.

Writes and reviews semantic, accessible HTML and template markup that stays readable and low-noise. Use when creating or refactoring HTML or Svelte templates, cleaning up div soup, choosing better elements, improving form markup, fixing heading or landmark structure, or replacing custom controls with native HTML.

Rewrite technical prose so it sounds specific, deliberate, and human instead of generic, formulaic, or AI-generated copy. Use when revising paragraph-level flow or voice in markdown posts under src/content/posts/**.

Guidance for modern JavaScript language features, modules, async code, and browser APIs. Use when building or reviewing general JavaScript for web apps, Node tools, or shared libraries, and when translating specs into practical patterns.

Create new or audit existing Agent Skills for GitHub Copilot with proper structure, frontmatter, and bundled resources. Use when asked to "create a skill", "make a new skill", "scaffold a skill", "audit a skill", or when building specialized AI capabilities. Generates SKILL.md files following the agentskills.io specification with Forward best practices for Salesforce development.

Designs or reviews user interfaces that are self-evident, low-friction, and easy to understand with minimal explanation. Use when simplifying UI text, removing helper copy, improving affordances, tightening hierarchy, making forms more obvious, or evaluating whether an interface works without instructions.