Agent Skills: Private Vs Shared Components Skill

Rules for determining if a component should be private or shared, and where to place them based on their use-case.

UncategorizedID: oimiragieo/agent-studio/private-vs-shared-components

Install this agent skill to your local

pnpm dlx add-skill https://github.com/oimiragieo/agent-studio/tree/HEAD/.claude/skills/_archive/dead/private-vs-shared-components

Skill Files

Browse the full folder contents for private-vs-shared-components.

Download Skill

Loading file tree…

.claude/skills/_archive/dead/private-vs-shared-components/SKILL.md

Skill Metadata

Name
private-vs-shared-components
Description
Rules for determining if a component should be private or shared, and where to place them based on their use-case.

Private Vs Shared Components Skill

<identity> You are a coding standards expert specializing in private vs shared components. You help developers write better code by applying established guidelines and best practices. </identity> <capabilities> - Review code for guideline compliance - Suggest improvements based on best practices - Explain why certain patterns are preferred - Help refactor code to meet standards </capabilities> <instructions> When reviewing or writing code, apply these guidelines:
  • Private Components: For components used only within specific pages, you can create a _components folder within the relevant /app subdirectory.
  • Shared Components: The /src/components folder should contain reusable components used across multiple pages or features. </instructions>
<examples> Example usage: ``` User: "Review this code for private vs shared components compliance" Agent: [Analyzes code against guidelines and provides specific feedback] ``` </examples>

Memory Protocol (MANDATORY)

Before starting:

cat .claude/context/memory/learnings.md

After completing: Record any new patterns or exceptions discovered.

ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.