skills/bityoungjae/domain-profiles/SKILL.md
Domain-specific configuration profiles for learning resource creation. Defines search strategies, special fields, terminology policies, and content structures for different academic domains: technology, history, science, arts, and general. Use when researcher or writer agents need domain-adapted behavior.
npx skillsauth add aiskillstore/marketplace domain-profilesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill provides domain-specific configurations for learning resource creation.
/init Phase 2 (Research Collection)| Profile | File | Description | | ---------- | ------------------------------ | ---------------------------------------------- | | Technology | technology.md | Programming, frameworks, tools, APIs | | History | history.md | Historical events, periods, civilizations | | Science | science.md | Physics, chemistry, biology, mathematics | | Arts | arts.md | Visual arts, music, performing arts | | General | language.md | General topics, linguistics, language learning |
Note: The "general" domain uses language.md profile, which contains broadly applicable patterns for educational content.
Each profile contains:
Authoritative sources and search query patterns for the domain.
Domain-specific metadata fields to collect and include.
How to handle technical terms, translations, and citations.
Recommended document organization and pedagogical approach.
All agents should load domain profiles using this standardized pattern:
Read("skills/domain-profiles/{domain}.md")
Domain to File Mapping:
| Input Domain | File to Read | |--------------|--------------| | technology | technology.md | | history | history.md | | science | science.md | | arts | arts.md | | general | language.md |
IMPORTANT: When domain is "general", agents MUST read language.md, not "general.md" (which doesn't exist).
| Agent | Sections to Extract | |-------|---------------------| | researcher | Search Strategy, Special Fields, Quality Indicators | | research-collector | Search Strategy, Special Fields | | writer | Content Structure, Terminology Policy | | reviewer | Review Criteria (Critical Checks, Quality Checks, Style Checks) |
# In researcher agent prompt
Read("skills/domain-profiles/technology.md")
# Extract Search Strategy section for domain-appropriate queries
# In writer agent prompt
Read("skills/domain-profiles/technology.md")
# Apply Content Structure and Terminology Policy to document
Domains are determined by the project-interviewer during the interview:
| Domain | Typical Topics | | ---------------- | -------------------------------------- | | technology | Python, React, Docker, API, 프로그래밍 | | history | 조선시대, 르네상스, 세계대전, 문명 | | science | 양자역학, 미적분, 세포생물학, 화학 | | arts | 유화, 작곡, 조각, 연기, 디자인 | | language/general | 언어학, 글쓰기, 일반 교양 |
If domain is unclear or "general", use:
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.