# .clinerules

**Canonical:** https://apis.io/providers/clinerules/  
**Website:** https://cline.bot  
**APIs profiled:** 0

.clinerules is the rule-file convention used by the Cline open-source AI coding agent. Projects expose persistent guidance to Cline by placing a .clinerules/ directory at the repository root containing one or more Markdown or text files. Each file may declare optional YAML frontmatter to scope its instructions to glob patterns so the agent only loads context relevant to the active task. The format is interoperable with AGENTS.md, .cursorrules, and .windsurfrules conventions, providing a cross-tool standard for codifying coding conventions, architectural decisions, and behavioural constraints for AI coding agents.

## Kin Score — 14.0 / 100 (emerging)

Scored 2026-08-20 under rubric 0.12.0. Trend: flat (+0.0 from 14.0).

| Facet | Score |
|---|---|
| Discoverability | 57.4 |
| Contract Quality | 7.0 |
| Governance | 9.8 |
| Contract Governance | 9.8 |
| Operational Transparency | 26.3 |
| Developer Ergonomics | 9.5 |
| Commercial Clarity | 0.0 |
| Access Clarity | 0.0 |

## Agent readiness — 0.0 (human-only)

| Dimension | Value |
|---|---|
| Spec Presence | no |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | no |
| Idempotency | no |
| Error Semantics | no |
| OpenAPI Examples | no |
| Rate Limit Signal | no |
| Event Surface Described | no |
| Agent Skills | no |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |

## Access

Unknown — onboarding: unknown, pricing: unknown, trial: no (confidence: low).

## Security (2)

- **Clinerules Domain Security** — TLSv1.3 · HSTS · DNSSEC · DMARC
- **Clinerules Vulnerability Disclosure** — Bugcrowd · security.txt · contact published

## Tags

AI Agents, Cline, Coding Standards, Configuration, Developer Workflow, Prompt Engineering

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/clinerules/). Scores are computed from the provider's own public artifacts under a published rubric.