[FEATURE] Add Cline support as a target agent

[v2cybersecurex]

Is your feature request related to a problem? Please describe.
I'm frustrated when managing AI agent packages with APM because Cline — one of the most widely used open-source AI coding agents — is not a supported target. There's no way to declare or install skills, prompts, and instructions specifically for Cline via apm.yml.

Describe the solution you'd like
Add cline as a recognized target agent in APM, similar to how copilot or claude are supported. This should include auto-detection (e.g. via .clinerules/ folder), proper output file generation, and CLI support (apm install --target cline).

Describe alternatives you've considered
N/A

Additional context
Add any other context or screenshots about the feature request here.

[github-actions]

Triage decision

needs-design

Proposed labels

theme/portability
area/multi-target
type/feature
status/needs-design

Milestone

null

Suggested next action

Document Cline's expected directory structure for rules/skills/agents and whether Cline has an MCP client config format, then identify which APM integrator pattern applies before implementation begins.

Suggested issue comment

Thanks for the request -- adding Cline is a natural extension of APM's multi-target philosophy. Cline is widely used and the feature request is aligned with APM's goal of supporting any AI coding agent.

Before we can implement this, we need a design comment that answers the following questions about what Cline expects:

1. **Skill/agent directory layout.** Where does Cline load rules, prompts, and instructions from? (e.g., `.clinerules/` for rules, but are there subdirectories for skills and agent configurations?)
2. **File format.** What file formats does Cline recognize? (Markdown `.md`? JSON? Custom format?)
3. **MCP client config.** Does Cline have its own MCP client config file (similar to `.cursor/mcp.json`)? If so, what is the schema and file path?
4. **Auto-detection signal.** You suggested `.clinerules/` -- is this the right marker? (A directory that is Cline-specific and unlikely to exist in non-Cline repos.)

Once these are documented (a short design comment here with links to the Cline docs is sufficient), the implementation follows the existing target integration pattern. You can look at `src/apm_cli/integration/targets.py` and the existing Claude adapter as a reference for what is needed.

If you are interested in contributing the implementation, we would love the help -- just resolve the design questions first and we can move forward together.

Per-lens notes (collapsed)

DevX UX Expert -- User-Need Reviewer

The user task is "install APM packages for use with Cline." Cline is a widely-used open-source VSCode AI agent extension. The feature request is clear and aligned with APM's "any AI agent" mission. The request is sparse on details about Cline's expected directory structure and MCP config format, which are required to implement the integration correctly. The npm/cargo mental model: the tool should install to exactly the path the target agent expects, not a guess.

Supply Chain Security Expert -- Risk-Surface Reviewer

Adding a new target means writing files to Cline-specific locations. The implementation must use validate_path_segments and ensure_path_within from src/apm_cli/utils/path_security.py for all path construction, per the centralized path safety rule. Auto-detection of .clinerules/ must be Cline-specific enough to avoid false positives. No specific supply-chain risk beyond standard target integration requirements.

OSS Growth Hacker -- Contributor-Tone Reviewer

v2cybersecurex has author_association: NONE -- this is their first or one of very few interactions with microsoft/apm. The issue is brief but clear. The response should warmly acknowledge the request, express genuine interest in adding Cline support, and give them a concrete next step (answer the design questions). The invitation to contribute is important: they may be the best person to answer the design questions since they use Cline.

Python Architect -- Architecture Reviewer

Adding Cline follows a well-understood pattern (new entry in targets.py, new ClineIntegrator or reuse of BaseIntegrator with Cline-specific paths, possibly a ClineClientAdapter if Cline has MCP support). The design is blocked on the Cline file layout and MCP config format. status/needs-design is correct: implement only after the target's expected layout is confirmed from the Cline documentation. The implementation scope will be clear once the design questions are answered.

Doc Writer -- Documentation Reviewer

Adding Cline will require a new section in the supported targets documentation and CLI reference updates. area/docs-site is omitted from the label set (within 6-label cap) but the implementing PR must include doc updates. The design comment should use the same "target" vocabulary as the existing multi-target documentation.

APM CEO -- Triage Arbiter

Right direction, right ask -- Cline is a legitimate and popular target. needs-design is the correct gate: the implementation is straightforward once the Cline file layout is confirmed, but shipping a Cline adapter with wrong paths would require a fast follow-up release. Growth Hacker recommendation: the response should explicitly invite v2cybersecurex to contribute the design comment and implementation, since they are the Cline user best positioned to answer the design questions.

{
  "decision": "needs-design",
  "decision_detail": "Document Cline's expected directory structure (rules, skills, agents), file formats, MCP client config schema (if any), and the auto-detection signal before implementation.",
  "theme": "theme/portability",
  "areas": ["area/multi-target"],
  "type": "type/feature",
  "status": "status/needs-design",
  "priority": null,
  "preserved_labels": [],
  "milestone": null,
  "next_action": "Post a design comment documenting Cline's expected file layout (directory structure, file formats, MCP config schema) with links to Cline docs.",
  "comment_markdown": "Thanks for the request -- adding Cline is a natural extension of APM's multi-target philosophy. Cline is widely used and the feature request is aligned with APM's goal of supporting any AI coding agent.\n\nBefore we can implement this, we need a design comment that answers the following questions about what Cline expects:\n\n1. **Skill/agent directory layout.** Where does Cline load rules, prompts, and instructions from? (e.g., `.clinerules/` for rules, but are there subdirectories for skills and agent configurations?)\n2. **File format.** What file formats does Cline recognize? (Markdown `.md`? JSON? Custom format?)\n3. **MCP client config.** Does Cline have its own MCP client config file (similar to `.cursor/mcp.json`)? If so, what is the schema and file path?\n4. **Auto-detection signal.** You suggested `.clinerules/` -- is this the right marker? (A directory that is Cline-specific and unlikely to exist in non-Cline repos.)\n\nOnce these are documented (a short design comment here with links to the Cline docs is sufficient), the implementation follows the existing target integration pattern. You can look at `src/apm_cli/integration/targets.py` and the existing Claude adapter as a reference for what is needed.\n\nIf you are interested in contributing the implementation, we would love the help -- just resolve the design questions first and we can move forward together."
}

---

Triage status: agentic proposal pending human ratification.
Silence is approval. Maintainers can:

• Override any label or milestone above by editing it directly --
  human edits are authoritative and will not be reverted on
  subsequent runs.
• Re-trigger triage by applying the status/needs-triage label, or
  by removing status/triaged to enroll the issue in the next
  daily sweep.

Posted by the Triage Panel workflow. See .apm/skills/apm-triage-panel for the panel skill.

Generated by Triage Panel · ● 2.3M · ◷