Extension Rules

Centralize Chrome extension architecture, permissions, rendering, and authentication rules into a specification.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/taikiwt/sitecue --skill extension-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Extension Rules
Source: https://github.com/taikiwt/sitecue/tree/main/.agent/skills/extension
Command: npx skills add https://github.com/taikiwt/sitecue --skill extension-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Extension Rules consolidate architecture, permission strategy, Markdown rendering, and authentication guidelines into a single, official reference to enable consistent development and safe practices.

Core Features & Use Cases

  • Centralized documentation of extension structure, including apps/extension, background and UI components.
  • Clear guidance on permissions minimization, dynamic permission requests, and secure API communication.
  • Standards for Markdown rendering (react-markdown with remark-breaks and remark-gfm) and authentication flow via Supabase.

Quick Start

Apply these rules to design, review, and maintain a Chrome extension that follows the architecture, permissions, and rendering guidelines.

Frequently Asked Questions about Extension Rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a Chrome extension with minimal permissions and secure authentication?

To structure a Chrome extension with minimal permissions, you need a centralized specification defining apps/extension components, background logic, and Supabase authentication. This provides actionable rules for dynamic permission requests and safe rendering to ensure compliant architecture.

What is the best way to manage dynamic permission requests in a browser extension?

Managing dynamic permission requests requires clear guidelines on permission minimization and secure API communication. Consolidating these rules into a single reference ensures your extension requests permissions dynamically while maintaining safe background and UI logic.

How does Markdown rendering work with react-markdown in a secure extension environment?

Markdown rendering in a secure extension environment works by standardizing on react-markdown with remark-breaks and remark-gfm. This ensures consistent formatting and safe UI logic within your extension architecture.

Can I use Supabase authentication with my Chrome extension's background logic?

Yes, you can use Supabase authentication with your Chrome extension by following defined authentication flow standards. Integrating Supabase requires secure API communication and background logic rules to maintain a compliant and safe extension architecture.

How do I review and maintain a Chrome extension for architecture and security compliance?

Reviewing and maintaining a Chrome extension for compliance involves applying centralized rules for architecture, permissions, and rendering. Using a single official reference allows you to validate front-end constraints and back-end security safeguards effectively.