| type | skill |
| name | project-context |
| description | Auto-triggered skill for project-specific facts, structure, and conventions |
| version | 0.2.0 |
| tags | ["project","context","configuration"] |
Project Context: aida-marketplace
This skill provides factual information about aida-marketplace's
structure, tooling, and conventions. All information here is either
auto-detected or explicitly configured for this project.
Project Facts
Project Name: aida-marketplace
Project Type: Unknown
Primary Language(s): TypeScript
Version Control: git
Project Structure
Source Code Organization
Source organization: Flat structure (no src/ directory)
Code organization pattern: Follow existing pattern
Documentation
Documentation: README.md only
README: README.md (1592 chars - Standard - README, API docs, inline comments)
Changelog: None (changes tracked in git commits)
License: LICENSE
Testing
Testing framework: Minimal - manual testing only
Tests: Not yet set up
Tools & Infrastructure
Build/Package Management: package.json (Node/npm)
Development Tools: Git, GitHub Actions
Docker
Docker: Not used
CI/CD
CI/CD: GitHub Actions
Issue Tracking
Issue Tracking System: GitHub Issues
MCP Integration: ✅ GitHub MCP (official)
Claude should:
- Reference issues using #issue-number format
- Include "Fixes #123" or "Closes #123" in commit messages
- Suggest issue labels and milestones
- Use GitHub MCP for issue management
Project Conventions
Standard conventions - follow typical open-source project conventions
API Documentation
Guidelines for Claude
When working in this project:
Code Structure:
-
Place new files following the "Follow existing pattern" organization pattern
-
Follow flat project structure
-
Create tests directory when adding first test
Documentation:
Testing:
- Follow Minimal - manual testing only approach
Conventions:
- Follow project-specific conventions documented above
Quality:
- Ensure CI/CD checks pass before committing