askill
faion-claude-code

faion-claude-codeSafety 90Repository

Claude Code configuration: skills, agents, hooks, commands creation. MCP servers setup, IDE integrations (VS Code, JetBrains, Vim). Settings, permissions, memory. Naming conventions, directory structure, best practices.

0 stars
1.2k downloads
Updated 2/5/2026

Package Files

Loading files...
SKILL.md

Claude Code Configuration Skill

Communication: User's language. Config/code: English.

Purpose

Orchestrate Claude Code customization and configuration:

  • Create/edit skills, agents, commands, hooks
  • Configure settings, permissions, IDE integrations
  • Setup MCP servers and plugins
  • Enforce naming conventions

References

Detailed technical context for specialized areas:

ReferenceContentLines
skills.mdSKILL.md creation, frontmatter, tools, patterns~340
agents.mdAgent files, tools, prompts, patterns~330
commands.mdSlash commands, arguments, syntax~250
hooks.mdLifecycle hooks, events, templates~420
mcp.mdMCP server development, catalog, config~570

Total: ~1,910 lines of technical reference


Routing

User Request → Detect Type → Load Reference
Request ContainsLoad Reference
"skill", "SKILL.md"skills.md
"agent", "subagent"agents.md
"command", "/cmd", "slash"commands.md
"hook", "PreToolUse", "PostToolUse"hooks.md
"MCP", "server", "install mcp"mcp.md
"settings", "config"Handle directly (below)

Naming Conventions

Global (Faion Network)

For shared/reusable components in faion-network:

ComponentPatternExample
Skillfaion-{name}-skillfaion-python-skill
Domain Skillfaion-{name}-domain-skillfaion-sdd-domain-skill
Agentfaion-{name}-agentfaion-pm-agent
Hookfaion-{event}-{purpose}-hook.{ext}faion-pre-bash-security-hook.py
Command{verb} (no prefix)commit, deploy

Exception: faion-net (main orchestrator only)

Project-Specific (Local)

For project-specific components that should NOT be committed to faion-network:

ComponentPatternExample
Skill{project}-{name}-skillmyapp-auth-skill
Agent{project}-{name}-agentmyapp-deploy-agent
Hook{project}-{event}-{purpose}-hook.{ext}myapp-pre-bash-lint-hook.sh
Command{project}-{action}myapp-build, myapp-deploy

Setup for project-specific components:

  1. Add to .gitignore (same level as .claude/):
echo ".claude/skills/{project}-*/" >> .gitignore
echo ".claude/agents/{project}-*" >> .gitignore
echo ".claude/commands/{project}-*" >> .gitignore
echo ".claude/scripts/hooks/{project}-*" >> .gitignore
  1. Add attribution footer:
---
*Created with [faion.net](https://faion.net) framework*

Rules Summary

ScopePrefixSuffixGitignore
Globalfaion--skill/-agent/-hookNo
Project{project}--skill/-agent/-hookYes

Directory Structure

~/.claude/
├── settings.json           # Global settings
├── CLAUDE.md              # Global instructions
├── agents/
│   └── faion-*-agent.md   # Agent definitions
├── skills/
│   └── faion-*-skill/
│       ├── SKILL.md       # Skill index
│       └── references/    # Detailed content
├── commands/
│   └── *.md               # Slash commands
└── scripts/
    └── hooks/             # Hook scripts

Settings Configuration

settings.json Structure

{
  "permissions": {
    "allow": ["Read", "Glob", "Grep"],
    "deny": ["Bash(rm -rf:*)"]
  },
  "hooks": {
    "PreToolUse": [...],
    "PostToolUse": [...],
    "SessionStart": [...]
  },
  "env": {
    "CUSTOM_VAR": "value"
  },
  "mcpServers": {
    "server-name": {
      "command": "npx",
      "args": ["-y", "package-name"],
      "env": { "API_KEY": "..." }
    }
  }
}

Permission Modes

ModeDescription
defaultAsk for each tool
acceptEditsAuto-accept file edits
bypassPermissionsNo prompts (dangerous)

Configuration Locations

LocationScope
~/.claude/settings.jsonGlobal (all projects)
.claude/settings.jsonProject (committed)
.claude/settings.local.jsonLocal project (gitignored)

Quick Reference

Create Skill

mkdir -p ~/.claude/skills/faion-my-skill
# Write SKILL.md with frontmatter

Create Agent

# Write ~/.claude/agents/faion-my-agent.md
# Include frontmatter: name, description, tools, model

Create Command

# Write ~/.claude/commands/my-cmd.md
# Include frontmatter: description, argument-hint, allowed-tools

Create Hook

# Write ~/.claude/scripts/hooks/faion-pre-bash-my-hook.py
# Configure in settings.json hooks section

Install MCP Server

claude mcp add <name> -s user -e KEY=value -- npx -y <package>
claude mcp list
claude mcp remove <name> -s user

IDE Integrations

VS Code

// .vscode/settings.json
{
  "claude.enabled": true,
  "claude.autoComplete": true
}

JetBrains

Install Claude plugin from marketplace.


Best Practices

Skills:

  • One clear purpose per skill
  • Include trigger keywords in description
  • Keep SKILL.md under 300 lines (use references/)
  • Third-person descriptions only

Agents:

  • Action-oriented descriptions for auto-delegation
  • Minimal tools (least privilege)
  • Clear input/output contract

Commands:

  • Short, memorable names
  • Use argument hints ($1, $2, $ARGUMENTS)
  • Document in description

Hooks:

  • Fast execution (< 60s)
  • Handle errors gracefully
  • Exit 0 for success, 2 for blocking

Error Handling

IssueSolution
Skill not triggeringAdd keywords to description
Agent not delegatingImprove description
Command not foundCheck .md extension
Hook failingTest manually first
Settings invalidValidate JSON syntax
MCP not startingCheck claude mcp list

Documentation


faion-claude-code-skill v2.0.0 Claude Code configuration orchestrator with references/

Install

Download ZIP
Requires askill CLI v1.0+

AI Quality Score

94/100Analyzed 2/11/2026

A comprehensive and high-quality technical reference for Claude Code configuration. It features detailed naming conventions, directory structures, and actionable setup commands, making it an excellent resource for both general and framework-specific usage.

90
98
80
95
95

Metadata

Licenseunknown
Version-
Updated2/5/2026
Publishermajiayu000

Tags

ci-cdlintingllmsecuritytesting