creating-continue-packages

Continue rules use glob patterns to match file paths and regex for content matching, enabling automatic application to specific files. Define the pattern in your rule configuration to target file types like `.tsx` or `.ts`, then set the `alwaysApply` behavior to control when the rule triggers.

The `alwaysApply` field has three distinct behaviors: `true` applies the rule unconditionally, `false` requires user confirmation, and `undefined` applies contextually based on file content. Choose the behavior that matches your rule's strictness and use case.

Extract metadata from your SKILL.md and related scripts to create a three-sentence request optimized for vector embedding, a description following the Action Input to Output pattern, and a toxicity analysis with explicit rationale for downstream retrieval systems.

Yes. Create context-aware rules with glob patterns targeting file types (e.g., all `.tsx` files) and regex matching for content patterns (e.g., React imports). Apply TypeScript standards or project-specific patterns automatically using appropriate `alwaysApply` settings.

Glob patterns match file paths and names (e.g., `src/**/*.tsx`), while regex matches content within files. Use globs to target which files the rule applies to, and regex to match specific code patterns or syntax within those files.

Semantic metadata enables RAG systems to retrieve and apply your rules precisely. Dense, structured descriptions with clear request-to-output mappings improve retrieval accuracy and ensure rules activate in the right contexts without ambiguity.