add-component
Skill4 starsChanged 4 months agoMITView on GitHub
Add a new pico-ioc component with dependency injection. Use when creating services, factories, interceptors, event subscribers, or configured settings.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- davision0102/fabriktheir own version, first seen Nov 15, 2026
- IntelliHelper/agent-skillstheir own version, first seen Oct 20, 2026
- jpicklyk/task-orchestratortheir own version, first seen Oct 17, 2026
- DailybotHQ/deepworkplan-websitetheir own version, first seen Oct 9, 2026
- Azure-Samples/art-voice-agent-acceleratortheir own version, first seen Oct 8, 2026
- lbedner/aegis-stacktheir own version, first seen Oct 8, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- signerlabs/ShipSwift★ 3.3ksame name
- jpicklyk/task-orchestrator★ 214same name
- lbedner/aegis-stack★ 146same name
- ahpxex/open-dashboard★ 136same name
- Azure-Samples/art-voice-agent-accelerator★ 74same name
- DailybotHQ/deepworkplan-website★ 15same name
- davision0102/fabrik★ 3same name
- IntelliHelper/agent-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- add-actuatorSkill
- add-appSkill
- add-authSkill
- add-celery-taskSkill
- add-controllerSkill
- add-repositorySkill
- add-server-authSkill
- add-testsSkill
- add-validationSkill
- init-projectSkill
- pico-conventionsSkill
- releaseSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Create a component: $ARGUMENTS
- Distinctive: line 12
Read the codebase to understand existing patterns, then create the component following these templates.
- Distinctive: line 38
Use when the component needs complex construction or wraps an external library:
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Add Pico-IoC Component
Create a component: $ARGUMENTS
Read the codebase to understand existing patterns, then create the component following these templates.
Basic Component
from pico_ioc import component
@component
class $ARGUMENTS:
def __init__(self, dependency: SomeDependency):
self.dependency = dependency
async def do_something(self) -> Result:
return await self.dependency.process()With Scope
@component(scope="singleton") # singleton | prototype | request
class $ARGUMENTS:
...Factory Provider
Use when the component needs complex construction or wraps an external library:
from pico_ioc import factory, provides
@factory
class InfraFactory:
@provides(ExternalClient, scope="singleton")
def create_client(self, settings: AppSettings) -> ExternalClient:
return ExternalClient(url=settings.url, timeout=settings.timeout)AOP Interceptor
from pico_ioc import component, MethodInterceptor, MethodCtx
@component(scope="singleton")
class LoggingInterceptor(MethodInterceptor):
async def invoke(self, ctx: MethodCtx, call_next):
print(f"Calling {ctx.method_name}")
result = await call_next(ctx)
return resultApply with @intercepted_by(LoggingInterceptor) on methods.
Configuration Dataclass
from dataclasses import dataclass
from pico_ioc import configured
@configured(prefix="section_name")
@dataclass
class MySettings:
host: str = "localhost"
port: int = 8080
debug: bool = FalseReads from YAML:
section_name:
host: "0.0.0.0"
port: 9090Event Subscriber
from pico_ioc import component, subscribe, Event
class OrderPlacedEvent(Event):
def __init__(self, order_id: int):
self.order_id = order_id
@component
class NotificationService:
@subscribe(OrderPlacedEvent)
async def on_order_placed(self, event: OrderPlacedEvent):
await self.notify(event.order_id)Checklist
- Scope matches lifecycle needs (singleton for stateless, prototype for stateful, request for per-request)
- Dependencies injected via constructor type hints
- Protocol/interface defined if multiple implementations exist
- Component is testable with mocked dependencies
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

