-
Notifications
You must be signed in to change notification settings - Fork 3
Core Concepts
CodingScaffold prefers local inference for routine work, but it can use cloud providers when the project allows that and credentials are available. This keeps sensitive or routine edits close to the machine while still leaving room for stronger models on architecture, security, and difficult reviews.
The scaffold keeps three ideas separate:
- provider: where the request is sent, such as Ollama, OpenAI, Anthropic, Azure OpenAI, or Azure AI
- model family: what kind of model answers, such as local, OpenAI, Anthropic, or Google
- deployment: a provider-specific name, common in Azure environments
This matters because Azure can be the endpoint while the deployed model family is OpenAI, Anthropic, or another model family.
Agentic coding is a workflow, not just a bigger prompt. A good loop has:
- context loading
- a small plan
- bounded edits
- local verification
- review
- a summary with changed files and residual risk
Skills are team-owned workflows encoded as reusable Markdown instructions. They are useful when a team repeats work such as release checks, dependency upgrades, incident reviews, or API contract changes.
Team memory should be durable, reviewable, and searchable. CodingScaffold uses Markdown as the source of truth and can shape that Markdown for plain Git, Obsidian, or MemPalace indexing.