compiler-development
Build NeverC or other LLVM compilers across frontend, IR, optimization, code generation, ABI, and target support. Use when the compiler pipeline is the subject; use narrower LLVM skills for isolated tooling or analysis.
소스 정보
- 저장소
- NeverSight/NeverC
- 최근 소스 활동
- 2026년 9월 13일 11:17
- 감지된 SKILL.md 언어
- 영어
- 스타
- 96
- 포크
- 11
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
파일 탐색기
5 개 파일SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- compiler-development
- description
- Build NeverC or other LLVM compilers across frontend, IR, optimization, code generation, ABI, and target support. Use when the compiler pipeline is the subject; use narrower LLVM skills for isolated tooling or analysis.
# Compiler development
Use this skill when a change crosses compiler stages or target boundaries. Keep source-language semantics, LLVM IR, ABI lowering, object format, linker behavior, and runtime assumptions owned by the narrowest authoritative layer.
## Topic routing
Read only the reference that matches the work:
- [Targets and ABI](references/targets-and-abi.md) for platform matrices, calling conventions, build-system target handling, and module metadata.
- [DynCode and testing](references/dyncode-and-testing.md) for cross-platform DynCode invariants and target-specific verification.
- [Compiler pipeline](references/compiler-pipeline.md) for frontend, AST, IR generation, optimization, JIT, and language implementation patterns.
- [Workflow and resources](references/workflow-and-resources.md) for broader compiler-development workflow and upstream references.
For an isolated pass use `llvm-optimization`; for Clang/LLDB/LSP developer tooling use `llvm-tooling`; for static or dynamic analyses use their narrower skills. Prefer current NeverC source and repository documentation over examples in these references.
GitHub에서 보기