refactor: remove plugins from profiles and update opencoder agent (#122 )

* refactor: remove plugins from profiles and update opencoder agent

- Remove plugin:notify, plugin:telegram-bot, and plugin:telegram-notify from Business, Full, and Advanced profiles
- Update opencoder agent to use ContextScout for discovery instead of 'DIGGING IN...' phrase
- Reduces profile component count and improves agent context discovery workflow

* feat: implement function-based context system with wildcard dependencies

## Context System Overhaul

### New Context Standards (3 files)
- Add frontmatter.md: HTML comment frontmatter format for all context files
- Add codebase-references.md: Standards for linking context to code implementation
- Update templates.md: Add frontmatter and codebase references to all 5 templates

### System Builder Updates
- Replace topic-based folders (domain/processes/standards/templates) with function-based folders (concepts/examples/guides/lookup/errors)
- Add navigation.md as REQUIRED file in all context structures
- Update validation rules: 4 → 8 checks (frontmatter, codebase refs, MVI limits)
- Update file size limits to match MVI principle per folder type
- Update architecture planning, context organization, and delivery stages

### Context Organizer Refactor
- Replace 27 individual dependencies with 1 wildcard: context:core/context-system/*
- Implement 9-step standards-based workflow with code discovery
- Add Step 0: Load standards via @ symbol
- Add Step 1: Discover codebase using glob patterns
- Update all generation steps to use templates with frontmatter + codebase refs
- Add comprehensive validation (frontmatter, codebase refs, MVI, file size)

### Registry Updates
- Add 2 new context entries: frontmatter, codebase-references
- Update context-organizer dependencies: 11 individual IDs → 1 wildcard pattern
- Simplify maintenance: auto-includes new context-system files

### Benefits
- Simpler maintenance: 27 lines → 2 lines in agent dependencies
- Better organization: Function-based structure (what/how/reference/troubleshooting)
- Auto-scaling: New context-system files automatically included
- Standards enforcement: Frontmatter and codebase references required
- Complete coverage: All context-system files discoverable via wildcard

### Other Changes
- Update ContextScout permissions and documentation
- Add visual-development.md context file
- Update design-iteration workflow
- Remove deprecated WORKFLOW_GUIDE.md
- Update README.md and developer profile

Co-authored-by: System Builder <system@openagents.dev>

* fix: add wildcard support to registry validation script

- Handle wildcard patterns in context dependencies (e.g., context:core/context-system/*)
- Extract prefix before wildcard and match against context file paths
- Prevents validation failures for wildcard dependencies in registry

---------

Co-authored-by: System Builder <system@openagents.dev>

2026-01-27 22:49:24 +00:00

3.1 KiB

Raw Blame History

name	description
context7	Retrieve up-to-date documentation for software libraries, frameworks, and components via the Context7 API. This skill should be used when looking up documentation for any programming library or framework, finding code examples for specific APIs or features, verifying correct usage of library functions, or obtaining current information about library APIs that may have changed since training.

Context7

Overview

This skill enables retrieval of current documentation for software libraries and components by querying the Context7 API via curl. Use it instead of relying on potentially outdated training data.

Workflow

Step 1: Search for the Library

To find the Context7 library ID, query the search endpoint:

curl -s "https://context7.com/api/v2/libs/search?libraryName=LIBRARY_NAME&query=TOPIC" | jq '.results[0]'

Parameters:

libraryName (required): The library name to search for (e.g., "react", "nextjs", "fastapi", "axios")
query (required): A description of the topic for relevance ranking

Response fields:

id: Library identifier for the context endpoint (e.g., /websites/react_dev_reference)
title: Human-readable library name
description: Brief description of the library
totalSnippets: Number of documentation snippets available

Step 2: Fetch Documentation

To retrieve documentation, use the library ID from step 1:

curl -s "https://context7.com/api/v2/context?libraryId=LIBRARY_ID&query=TOPIC&type=txt"

Parameters:

libraryId (required): The library ID from search results
query (required): The specific topic to retrieve documentation for
type (optional): Response format - json (default) or txt (plain text, more readable)

Examples

React hooks documentation

# Find React library ID
curl -s "https://context7.com/api/v2/libs/search?libraryName=react&query=hooks" | jq '.results[0].id'
# Returns: "/websites/react_dev_reference"

# Fetch useState documentation
curl -s "https://context7.com/api/v2/context?libraryId=/websites/react_dev_reference&query=useState&type=txt"

Next.js routing documentation

# Find Next.js library ID
curl -s "https://context7.com/api/v2/libs/search?libraryName=nextjs&query=routing" | jq '.results[0].id'

# Fetch app router documentation
curl -s "https://context7.com/api/v2/context?libraryId=/vercel/next.js&query=app+router&type=txt"

FastAPI dependency injection

# Find FastAPI library ID
curl -s "https://context7.com/api/v2/libs/search?libraryName=fastapi&query=dependencies" | jq '.results[0].id'

# Fetch dependency injection documentation
curl -s "https://context7.com/api/v2/context?libraryId=/fastapi/fastapi&query=dependency+injection&type=txt"

Tips

Use type=txt for more readable output
Use jq to filter and format JSON responses
Be specific with the query parameter to improve relevance ranking
If the first search result is not correct, check additional results in the array
URL-encode query parameters containing spaces (use + or %20)
No API key is required for basic usage (rate-limited)

3.1 KiB Raw Blame History