'relationship' 검색 결과

Author the Salesforce Configuration Workbook — the structured, reviewable handoff document an admin uses to execute a feature across Objects/Fields, Page Layouts, Profiles/PSGs, Sharing, Validation, Automation, List Views, Reports, Integrations, and Data. Triggers: 'salesforce configuration workbook', 'admin handoff document', 'implementation workbook'. NOT for object design itself (use admin/custom-field-creation, admin/lookup-and-relationship-design, agents/object-designer/AGENT.md), NOT for permission set design (use admin/permission-set-architecture, agents/permission-set-architect/AGENT.md), NOT for Flow construction (use skills/flow/* and agents/flow-builder/AGENT.md), and NOT for the deployment manifest (use skills/devops/metadata-api-retrieve-deploy). More triggers: workbook row schema, recommended_agent, recommended_skills, row_id, source_req_id, RTM linkage block, not-in-scope-this-release, descope ledger, version-lock the workbook, check_workbook.py.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when creating a new custom field on any Salesforce object: choosing field type, setting API name, configuring Field-Level Security, adding to page layouts, and deploying. Triggers: 'add a field', 'new custom field', 'what field type should I use', 'FLS not working', 'field not showing on page layout'. NOT for creating the object itself - use admin/object-creation-and-design. NOT for formula field logic - use admin/formula-fields. NOT for picklist value set management - use admin/picklist-and-value-sets. Also covers: field-meta.xml, CustomField metadata, deleteConstraint, externalId, unique, precision and scale, relationshipOrder, writeRequiresMasterRead, fieldPermissions, package.xml for fields.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when designing deployable Salesforce configuration with Custom Metadata Types, especially when choosing between CMTs, Custom Settings, and Custom Objects, protecting packaged defaults, or exposing config to Apex, Flow, and formulas. Triggers: 'custom metadata vs custom settings', 'deployable config', 'protected custom metadata', 'feature flags in Salesforce'. NOT for hierarchical Custom Settings resolution, getInstance/getValues, or their SOQL cost — use admin/custom-metadata-types-and-settings. NOT for high-churn transactional or user-managed business records — use admin/object-creation-and-design. NOT for secrets — use integration/named-credentials-setup. More trigger keywords: __mdt, CustomMetadata .md file, customMetadata folder, getInstance, getAll, xsi:type, visibility PackageProtected, MetadataRelationship, EntityDefinition field, $CustomMetadata.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate a data dictionary documenting entities, fields, and business rules. Use when the user says "data dictionary", "document the data model", "what fields are in this table", "data definitions", "field descriptions", "CRUD matrix", "entity relationship", "data catalogue", "what data does this system store" - even if they don't explicitly say "data dictionary".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Define the scope, success criteria, roles, and boundaries for a consulting engagement. Use when a consultant says "help me scope this engagement", "I need to define what's in and out", "the client keeps adding things", "scope is getting fuzzy", "we need a contracting conversation", "I'm not sure what we actually agreed to", "help me set boundaries with a client", or "what should be in a kickoff". Also trigger when describing an engagement that feels like it is expanding without agreement, or when starting a new client relationship and preparing the initial contract or SOW.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

โค้ชความสัมพันธ์ — คู่รัก ครอบครัว เพื่อน — ใช้ NVC, I-statements, Love Languages, conflict resolution

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Franchise Owner Playbook — franchise evaluation, SOP, multi-unit operations, franchisor relationship, ROI analysis สำหรับเจ้าของแฟรนไชส์ไทย

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert in language and culture relationships, sociolinguistics, and language variation across communities

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze vendor management systems for performance scorecards, third-party risk assessment, SLA enforcement, vendor rationalization, and relationship governance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit pharmaceutical yield prediction systems and process analytical technology -- evaluate critical process parameter (CPP) to critical quality attribute (CQA) relationships, design space characterization per ICH Q8(R2) Quality by Design, PAT sensor readiness (NIR, Raman.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user provides a plot summary, scene idea, character relationship, emotional beat, or short video concept and wants a cinematic AI video prompt. First diagnose the story, then rewrite it into a model-ready prompt for Kling, Seedance, Veo, Sora, Runway, Jimeng, or general AI video models.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Obsidian Claw is an ontology-building skill that transforms chaotic notes, raw ideas, voice dumps, and meeting transcripts into a structured, interlinked knowledge base inside Obsidian. Use this skill whenever the user wants to: add new notes to their Obsidian vault and auto-link them to existing ones, build a concept graph or knowledge map, surface forgotten related discussions ("you talked about this with investor X 3 months ago"), extract entities and relationships from unstructured text, or turn scattered thoughts into wiki-style atomic notes. Also trigger when the user mentions "second brain", "Zettelkasten", "PKM", "personal knowledge management", "note graph", "knowledge graph", "link my notes", "organize my vault", "connect ideas", or asks Claude to "remember" something across sessions using Obsidian. If the user is doing anything with Obsidian notes and wants intelligence layered on top, use this skill.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Author and own ONE content type's typed schema (the CONTENT-TYPE.md) at .unikit/gamedesign/content-types/CT-<slug>.md — the content / catalog layer of the GDD (cards, items, weapons, enemies, levels, quests, loot). Use whenever the user wants to ADD a new kind of content or UPDATE its schema, e.g. "add a new content type", "design the loot content", "define the card schema", "add an enemies content type", "add a rarity field to items", "switch this catalog to curated". Create the skeleton, fill its typed field schema (CT.fields), scale, relationships, and validation, AND revise the schema under the delta discipline (a schema change bumps the version + changelog). Selects the scale (bulk | curated) and self-registers content_types/content. This owns the content SCHEMA, not the catalog of values — adding individual entries/units is data handled in the editor, not a schema edit. To add or detail a system use /unikit-gd-system; to add a flow use /unikit-gd-flow; to apply a multi-zone edit use /unikit-gd-apply.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Persistent, adaptive vector memory for agents on a ruOS desktop — a Rust-native vector database with local semantic embeddings, HNSW retrieval, and graph relationships. Use to remember and recall across sessions with no database server or API key.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reorganize the user's X and LinkedIn network with review-first pruning, add/follow recommendations, and channel-specific warm outreach drafted in the user's real voice. Use when the user wants to clean up following lists, grow toward current priorities, or rebalance a social graph around higher-signal relationships.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

You are an AP process optimizer. When the user describes their payable workflows, vendor relationships, or payment processes, generate a complete accounts payable management framework.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Map UI elements and code relationships (affordances).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Automate Attio CRM operations -- search records, query contacts and companies with advanced filters, manage notes, list attributes, and navigate your relationship data -- using natural language through the Composio MCP integration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to "diagram", "visualize", "model", "map out", "show the flow", or when explaining system architecture, database design, code structure, or user/application flows.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create clear architecture views of Azure resources and their relationships. Use this skill when users ask for diagrams, topology summaries, dependency maps, or deployment overviews. Generates Mermaid, ASCII, and structured documentation for architecture review and compliance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage feature manifests for code traceability. Use when creating new features, updating existing features, checking feature health, or exploring the feature-to-code relationship. Activates for manifest validation, feature creation, changelog updates, and traceability queries.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Master of text-based visual communication using ASCII art, Unicode box-drawing, and structured diagram notation. Creates clear, maintainable diagrams for systems, processes, hierarchies, relationships, and psychological structures. Proactively generates diagrams to enhance understanding. Activate on visualization needs, system architecture, process flows, psychological mapping, or when complex concepts would benefit from visual representation. NOT for photo editing, vector graphics, or GUI-based design tools.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Temporal interval algebra for reasoning about time relationships in planning and knowledge representation

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Compare gene co-expression and regulatory networks between biological conditions to find rewired relationships using DiffCorr, DiffCoEx, DINGO/iDINGO, and CoDiNA. Covers the differential-connectivity-is-not-differential-expression distinction, the pairwise multiple-testing explosion, marginal vs partial (direct) rewiring, and the underpowered-rewiring failure mode. Use when comparing co-expression networks between disease vs control, treatment, or developmental stages, or finding hub genes that rewire without changing mean expression. For single-condition modules see coexpression-networks; for differential expression of means see differential-expression/de-results.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.