all publishers

Impertio-Studio

@impertio-studio source repo

858 published skills · page 8 of 9

  1. ▌
    Ifc Agents File Validator · impertio-studio bundle
    Use when asked to validate an IFC file, check whether an IFC model is conformant, run a pre-delivery quality gate on an IFC file, decide if an IFC file is valid, or triage a buildingSMART validation report. Prevents skipping the STEP-syntax gate, treating a warning as a file-invalidating error, reading a hidden pass as a skipped check, validating against the wrong schema, and confusing schema conformance with project information requirements. Covers the buildingSMART five-stage validation pipeline (STEP syntax, schema, normative, industry practice, bSDD), the Gherkin functional-part coverage map, the fifteen-item anti-pattern checklist, finding triage by severity, and routing each fault class to the matching ifc-errors skill, across IFC2x3, IFC4 and IFC4.3. Keywords: validate IFC file, is my IFC file valid, IFC validation pipeline, buildingSMART validation service, IFC conformance check, validation report triage, pre-delivery quality gate, schema validation, Gherkin normative rules, implementer agreement, inf
    203 repo stars
  2. ▌
    Ifc Core Standards Overview · impertio-studio bundle
    Use when you need to explain what IFC is, choose which IFC version to target, or understand how the buildingSMART ecosystem (software certification, validation service, schema repositories) fits together before authoring or reading IFC data. Prevents treating IFC as a runtime, a geometry kernel, a library API, or a single file format, and prevents targeting a withdrawn or non-official version. Covers the IFC data-model definition, the ISO 16739-1 standardization history, the three officially-supported versions, the three built-environment data dimensions, and the certification, validation, and schema-repository ecosystem. Keywords: IFC, Industry Foundation Classes, ISO 16739-1, buildingSMART, openBIM, IFC2x3, IFC4, IFC4.3, IFC5, IFCx, IFC version selection, what is IFC, which IFC version should I use, is IFC a file format, IFC standard explained, ISO PAS 16739, validation service, software certification, my IFC file will not validate, which version did this tool export, openBIM cornerstone.
    203 repo stars
  3. ▌
    Ifc Impl Format Transcoding · impertio-studio bundle
    Use when converting an IFC model between encodings (SPF .ifc, ifcXML, ifcJSON, ifcZIP) and the result must stay faithful, and when deciding which on-disk format to pick for a given exchange. Prevents confusing a format transcode with a schema-version migration, expecting STEP #id numbers to survive a round-trip, treating ifcJSON as a guaranteed lossless format, and assuming DERIVE or INVERSE attributes are lost in conversion. Covers the format comparison matrix, the EXPRESS schema as the single canonical model, SPF to ifcXML conversion (ISO 10303-28 plus the Part 28 configuration file), SPF or ifcXML to ifcJSON (provisional), ifcZIP wrapping, what is and is not preserved, and the transcoding vs version-migration vs geometry-export split. Keywords: IFC format conversion, transcoding, SPF to ifcXML, ifc to json, ifcXML, ifcJSON, ifcZIP, ISO 10303-28, Part 28 configuration file, lossless, round-trip, "which IFC format", "convert ifc file", "ifc file too big", "json instead of ifc", "lost data after conversion",
    203 repo stars
  4. ▌
    Ifc Syntax Georeferencing · impertio-studio bundle
    Use when you need to anchor an IFC model to real-world geographic coordinates : declare where the local project origin sits on Earth, rotate the model onto a map grid, pick between coarse site latitude/longitude and a precise projected CRS, or place infrastructure objects along an alignment by station and offset. Prevents treating the coarse IfcSite latitude as precise georeferencing, applying the map-conversion translation and rotation in the wrong order, mixing signs in a compound plane angle, targeting a map conversion at a non-projected CRS, emitting IFC4 or IFC4.3 georeferencing entities into an IFC2x3 file, and authoring geometry at raw projected coordinates. Covers IfcSite RefLatitude / RefLongitude / RefElevation, IfcCompoundPlaneAngleMeasure, IfcMapConversion, IfcProjectedCRS, IfcCoordinateReferenceSystem, IfcCoordinateOperation, IfcMapConversionScaled, the IFC4.3 IfcLinearPlacement family, the LoGeoRef levels, and the IFC2x3 / IFC4 / IFC4.3 version differences. Keywords: IFC georeferencing, IfcMapCo
    203 repo stars
  5. ▌
    Ifc Agents Quality Checker · impertio-studio bundle
    Use when an IFC file is schema-valid but you must judge whether it is actually useful, audit an IFC model for information completeness, score model quality before handover, or answer why a valid IFC file is empty in facility management, quantity take-off, or analysis software. Prevents confusing schema validity with information completeness, declaring a model "good" because it passed validation, auditing project-specific demands that belong to IDS, and shipping a model whose elements carry no properties, materials, classifications, quantities, or georeferencing. Covers a cross-skill model-quality audit across seven completeness dimensions (spatial containment, property sets, geometry representation, materials, classifications, quantities, georeferencing), a deterministic weighted scoring rubric, the validity-versus-completeness-versus-IDS three-tier model, and routing each gap to the owning skill, across IFC2x3, IFC4 and IFC4.3. Keywords: IFC quality check, IFC model audit, information completeness, model qua
    203 repo stars
  6. ▌
    Ifc Errors Encoding Issues · impertio-studio bundle
    Use when an IFC file is rejected at the STEP-syntax stage of validation, a parser reports a string or header error, accented or non-ASCII text shows up as garbage characters, or the file fails before any schema check runs. Prevents writing an un-doubled apostrophe or backslash inside a STEP string, breaking a \X2\ or \X4\ escape with a missing \X0\ terminator, shipping mojibake from a UTF-8 versus Latin-1 mismatch, sending a malformed FILE_DESCRIPTION, FILE_NAME, or FILE_SCHEMA header, and hunting for a non-existent IfcFileDescription entity. Covers STEP Physical File string escaping failure modes, the three header entities and their EXPRESS, the empty-description rejection, a missing or lowercase FILE_SCHEMA identifier, a byte-order mark before the magic token, and why a stage-1 STEP syntax error blocks the file before schema validation. Keywords: IFC encoding error, STEP syntax error, string escaping, \X2\, \X4\, \X0\ terminator, doubled apostrophe, mojibake, character encoding mismatch, UTF-8, Latin-1, FIL
    203 repo stars
  7. ▌
    Ifc Errors Geometry Issues · impertio-studio bundle
    Use when an IFC model loads blank in a viewer, geometry is missing, garbled, off-scale, mispositioned, or silently dropped on import, or a buildingSMART validation report flags a GEM rule. Prevents shipping shape representations with no representation context, placement chains that mix 2D and 3D, non-watertight Breps, degenerate or duplicated geometry, and geometry that the declared MVD forbids. Covers GEM051 and GEM052 missing or wrong context, IfcLocalPlacement chain errors and dimension mismatch, IfcFacetedBrep watertight-shell rules, GEM111, GEM112 and GEM113 duplicated and colinear points, zero-area faces and non-manifold solids, and MVD geometry mismatch across IFC2x3, IFC4 and IFC4.3. Keywords: IFC geometry error, nothing shows in viewer, blank model, empty model, model off by 1000x, geometry dropped on import, GEM051, GEM052, GEM111, GEM112, GEM113, representation context missing, IfcGeometricRepresentationContext, invalid placement chain, non-watertight shell, non-manifold solid, zero-area face, dege
    203 repo stars
  8. ▌
    Ifc Impl Geometry Extraction · impertio-studio bundle
    Use when extracting the geometry of an IFC element from an existing file in order to render it, mesh it, or measure it: resolving IfcProduct.Representation to its shape items, picking the right representation, walking the IfcLocalPlacement chain to a world transformation matrix, and decoding each RepresentationType (SweptSolid, Brep, Tessellation, CSG/Clipping, MappedRepresentation). Prevents every extracted element piling up at the origin because the placement chain was skipped, a blocky model because the Box representation was read instead of Body, scrambled meshes from treating IFC indices as zero-based, empty geometry because IfcMappedItem instances were not resolved, and wrong volumes from treating a tessellated approximation as an exact solid. Covers the product-to-shape resolution path, RepresentationIdentifier and RepresentationType, the placement-to-matrix computation, mapped-item transforms, and the IFC2x3 versus IFC4 versus IFC4.3 differences. Keywords: extract IFC geometry, IfcShapeRepresentation,
    203 repo stars
  9. ▌
    Ifc Impl Property Extraction · impertio-studio bundle
    Use when reading property sets, quantities, or effective attribute values out of an IFC model and the extracted values look wrong, incomplete, empty, or missing. Prevents reading only occurrence property sets while ignoring inherited type defaults, using IsDefinedBy to reach the type in IFC4 and IFC4.3, treating an IfcElementQuantity as an IfcPropertySet, and forgetting to expand an IfcPropertySetDefinitionSet bundled inside one relationship. Covers the IsDefinedBy / IsTypedBy traversal, the type vs occurrence override resolution algorithm, reading IfcElementQuantity, resolving a property value unit, IfcPropertySetDefinitionSet expansion, standard Pset_ vs custom property sets, and the IFC2x3 vs IFC4 inverse-attribute split. Keywords: property extraction, read property set, IfcRelDefinesByProperties, IsDefinedBy, IsTypedBy, HasPropertySets, IfcElementQuantity, IfcPropertySet, type vs occurrence override, Pset_WallCommon, quantity takeoff, NominalValue, resolve unit, "property is missing", "value is empty", "w
    203 repo stars
  10. ▌
    Ifc Syntax Classifications · impertio-studio bundle
    Use when you need to attach a classification code (Uniclass, OmniClass, MasterFormat, ETIM) or an external library reference to objects in an IFC model, or read and debug the classification and library entities of an existing model. Prevents putting the code in the wrong attribute, inventing IFC entity names, using the IFC2x3 attribute name in an IFC4 file (ItemReference vs Identification, Location vs Specification), and confusing the classification system entity with a single classification code. Covers IfcClassification, IfcClassificationReference, IfcRelAssociatesClassification, the IfcClassificationSelect and IfcClassificationReferenceSelect select types, the library entities IfcRelAssociatesLibrary, IfcLibraryReference and IfcLibraryInformation, the external systems Uniclass 2015 / OmniClass / MasterFormat / ETIM, and the IFC2x3 / IFC4 / IFC4.3 version differences. Keywords: IFC classification, IfcClassification, IfcClassificationReference, IfcRelAssociatesClassification, IfcClassificationSelect, IfcClas
    203 repo stars
  11. ▌
    Ifc Errors Version Mismatch · impertio-studio bundle
    Use when an IFC file fails validation because the declared FILE_SCHEMA does not match the entities used, when a file written for one schema is read with another schema's expectations, or when a model uses an entity that is deprecated or removed for its declared version. Prevents writing IfcBuildingElement into an IFC4.3 file, declaring IFC4 in the header while using IFC2x3-only entities, assuming OwnerHistory is mandatory in IFC4, copying DERIVED attribute slots blindly during migration, and treating a legacy IfcMaterialList as a hard error. Covers the FILE_SCHEMA token per version, the hard renames between IFC2x3, IFC4 and IFC4.3, deprecated and removed entities per version, attribute optionality and type changes across versions, the DERIVED attribute asterisk trap, and how to detect version inconsistency in an existing file. Keywords: IFC version mismatch, FILE_SCHEMA, IFC2X3, IFC4, IFC4X3_ADD2, deprecated entity, removed entity, IfcBuildingElement, IfcBuiltElement, IfcWallStandardCase, StandardCase removed
    203 repo stars
  12. ▌
    Ifc Errors Broken References · impertio-studio bundle
    Use when an IFC file has a reference that points nowhere, a parser crashes on an unresolved #id, or an element silently disappears from a downstream tool (no material, no property set, no spatial location) even though the file is schema-valid. Prevents treating a dangling #id and a missing INVERSE link as the same bug, trusting a "valid" verdict to mean the model is complete, and creating a relationship with the Relating and Related roles swapped. Covers the reference-graph nature of the STEP instance model, dangling and wrong-typed #id references, missing IfcRel* relationship entities, why a missing INVERSE attribute is a silent failure, detection scans, and fixes, across IFC2x3, IFC4 and IFC4.3 including the IfcBuildingElement to IfcBuiltElement rename. Keywords: dangling reference, broken #id, unresolved reference, missing INVERSE link, IfcRelContainedInSpatialStructure, IfcRelAssociatesMaterial, IfcRelDefinesByProperties, orphan element, element has no material, element has no property set, element not in
    203 repo stars
  13. ▌
    Ifc Errors Schema Validation · impertio-studio bundle
    Use when an IFC file fails schema validation or a buildingSMART validation report shows errors, and the cause is a WHERE-rule break, a global-rule break, an abstract-entity instantiation, a cardinality violation, or a wrong attribute type. Prevents instantiating an abstract supertype, calling an IFC4.3 IfcBuiltElement instantiation a schema error, ignoring the warning-vs-error distinction, and reading a validation report as if hidden passes were missing checks. Covers EXPRESS WHERE rules and global RULEs, abstract supertypes per version, attribute cardinality and type errors, the buildingSMART validation pipeline and its severities, the Gherkin normative-rule layer, running a single Gherkin rule locally, and Implementer Agreements versus Informal Propositions. Keywords: IFC schema validation, WHERE rule violation, global rule, abstract entity, IfcBuildingElement, IfcBuiltElement, cardinality, wrong attribute type, buildingSMART validation service, Gherkin rules, implementer agreement, informal proposition, "f
    203 repo stars
  14. ▌
    Ifc Errors Spatial Structure · impertio-studio bundle
    Use when IFC elements do not appear in a viewer's model tree, are missing from quantity take-off or facility-management exports, or a buildingSMART validation report flags spatial-structure problems : orphan elements with no spatial container, one element contained in two places at once, an element placed at the wrong spatial level, a deprecated proxy used as a placeholder, or a missing or broken spatial tree. Prevents shipping orphan elements with no IfcRelContainedInSpatialStructure link, mislabelling double containment as a WR31 violation, attaching physical elements with IfcRelAggregates instead of IfcRelContainedInSpatialStructure, using IfcBuildingElementProxy as a void or clearance placeholder in IFC4.3, and building a spatial tree that never reaches IfcProject. Covers orphan-element detection, the IfcElement.ContainedInStructure SET [0:1] inverse, WR31 and WR41, the IfcProject NoDecomposition rule, the IfcSingleProjectInstance global rule, IfcRelReferencedInSpatialStructure for multi-storey elements,
    203 repo stars
  15. ▌
    Ifc Impl Spatial Decomposition · impertio-studio bundle
    Use when authoring an IFC file and you must build the spatial breakdown tree and place every physical element into it, or when a wall, slab, or door does not show up in a viewer because it has no storey. Prevents orphan elements, double containment, placing elements with IfcRelAggregates instead of IfcRelContainedInSpatialStructure, and reversing the Relating and Related roles. Covers the top-down build order, IfcRelAggregates wiring, single-container placement, IfcRelReferencedInSpatialStructure for multi-storey elements, the IFC4.3 IfcFacility and IfcFacilityPart tree, and the orphan-check verification step. Keywords: IfcRelAggregates, IfcRelContainedInSpatialStructure, IfcRelReferencedInSpatialStructure, IfcProject, IfcSite, IfcBuilding, IfcBuildingStorey, IfcSpace, IfcFacility, IfcFacilityPart, spatial decomposition, spatial breakdown, build the spatial tree, place element in storey, orphan element, element not in viewer, wall has no storey, element missing from model, how do I add a wall to a storey, mul
    203 repo stars
  16. ▌
    Ifc Syntax Building Elements · impertio-studio bundle
    Use when you need to create, place, or debug a physical construction element in an IFC model : a wall, slab, beam, column, member, plate, door, window, roof, covering, stair, railing, footing, or proxy, including the type object, the PredefinedType enumeration, the spatial containment link, and the opening / void / fill triad for a door or window in a wall. Prevents using the removed name IfcBuildingElement in an IFC4.3 file (it was renamed IfcBuiltElement), leaving an element orphaned with no spatial container, reversing the IfcRelVoidsElement and IfcRelFillsElement anchors, setting PredefinedType to USERDEFINED without an ObjectType, and using a deleted *StandardCase entity. Covers IfcWall, IfcSlab, IfcBeam, IfcColumn, IfcMember, IfcPlate, IfcDoor, IfcWindow, IfcRoof, IfcCovering, IfcStair, IfcRailing, IfcFooting, IfcBuildingElementProxy, the matching type objects and PredefinedType enums, IfcOpeningElement, IfcRelContainedInSpatialStructure, IfcRelVoidsElement, IfcRelFillsElement, the IFC4.3 infrastructure
    203 repo stars
  17. ▌
    Ifc Syntax Geometry Profiles · impertio-studio bundle
    Use when you need to define, choose, or debug a 2D cross-section profile in an IFC model : a rectangle or circle profile, a standard steel section (I, L, U, T, C, Z), a hollow section, an arbitrary free-form outline, a profile with holes, or a composite or derived profile. Prevents feeding a CURVE-type or open profile into a solid sweep, using an IfcLine as a profile boundary, declaring a hollow wall thicker than its radius, nesting a composite profile inside another composite, and mixing AREA and CURVE profiles in one composite. Covers IfcProfileDef and IfcProfileTypeEnum, IfcParameterizedProfileDef and the eleven concrete parameterized profiles, IfcArbitraryClosedProfileDef, IfcArbitraryOpenProfileDef, IfcArbitraryProfileDefWithVoids, IfcCompositeProfileDef, IfcDerivedProfileDef, and the IFC2x3 / IFC4 / IFC4.3 version differences. Keywords: IFC profile, IfcProfileDef, IfcProfileTypeEnum, AREA, CURVE, IfcParameterizedProfileDef, IfcRectangleProfileDef, IfcCircleProfileDef, IfcIShapeProfileDef, IfcLShapeProfi
    203 repo stars
  18. ▌
    Ifc Syntax Geometry Placement · impertio-studio bundle
    Use when you need to position an IFC product in space, build or read the placement tree, or resolve an element to world coordinates : the door placed relative to its wall, the wall relative to its storey, the storey relative to the building, and so on up to the project world coordinate system. Prevents the placement errors that put elements in the wrong spot : a 3D placement chained to a 2D parent, a circular PlacementRelTo reference, supplying only one of Axis and RefDirection, forgetting to multiply the whole chain, and confusing the local geometry origin with the world position. Covers IfcObjectPlacement, IfcLocalPlacement (PlacementRelTo chaining and RelativePlacement), IfcAxis2Placement3D and IfcAxis2Placement2D with the right-handed axis derivation, IfcCartesianPoint, IfcDirection, IfcGridPlacement and IfcVirtualGridIntersection, and the IFC2x3 / IFC4 / IFC4.3 version differences. Keywords: IFC placement, IfcObjectPlacement, IfcLocalPlacement, PlacementRelTo, RelativePlacement, IfcAxis2Placement3D, IfcA
    203 repo stars
  19. ▌
    Ifc Syntax Step Physical File · impertio-studio bundle
    Use when reading, writing, or debugging the .ifc STEP Physical File: the ISO-10303-21 skeleton, the HEADER section (FILE_DESCRIPTION, FILE_NAME, FILE_SCHEMA), the DATA section instance syntax, the special tokens, value notation, string escaping, or the ifcZIP container. Prevents emitting attributes out of declared order, serializing inverse or derived attributes, confusing the unset token with the derived token, writing raw non-ASCII bytes into a string, and putting more than one model file in an ifcZIP. Covers the file skeleton, the three header entities and the ViewDefinition convention, hash-id instance syntax, forward and backward references, dollar and asterisk tokens, enum and boolean dot notation, typed-value wrapping, aggregates, the control directives, and PKZip 2.04g ifcZIP packaging. Keywords: STEP physical file, SPF, .ifc, ISO 10303-21, Part 21, ISO-10303-21, HEADER, DATA, ENDSEC, FILE_DESCRIPTION, FILE_NAME, FILE_SCHEMA, ViewDefinition, positional attributes, dollar sign, asterisk, forward refere
    203 repo stars
  20. ▌
    Ifc Syntax Geometry Swept Solid · impertio-studio bundle
    Use when you need to build, read, or debug parametric solid geometry in an IFC model : extruding a profile into a wall or slab, revolving a profile into an arch, sweeping a profile along a curve, or modelling a pipe or rebar as a swept disk, and when deciding the RepresentationType label for the shape. Prevents feeding a CURVE-type (open) profile into a solid sweep, an extrusion direction perpendicular to Z, a revolution axis outside the XY plane, an unbounded directrix with no parameters, an InnerRadius larger than the Radius, and mislabelling an advanced sweep as plain SweptSolid. Covers IfcSweptAreaSolid, IfcExtrudedAreaSolid, IfcRevolvedAreaSolid, IfcExtrudedAreaSolidTapered, IfcRevolvedAreaSolidTapered, IfcDirectrixCurveSweptAreaSolid, IfcSurfaceCurveSweptAreaSolid, IfcFixedReferenceSweptAreaSolid, IfcSweptDiskSolid, the SweptArea / Position / ExtrudedDirection / Depth / Axis / Angle / Directrix / Radius attributes, the WHERE rules, the SweptSolid versus AdvancedSweptSolid mapping, and IFC2x3 / IFC4 / IF
    203 repo stars
  21. ▌
    Ifc Errors Property Set Mistakes · impertio-studio bundle
    Use when an IFC file fails validation on a property set, quantity set or material association, or when a custom property set is rejected, ignored, or collides with the standard library, or a layered-material assignment breaks a WHERE rule. Prevents naming a custom property set with the reserved Pset_ prefix, pointing IfcRelDefinesByProperties at a type object, attaching IfcMaterialLayerSetUsage to a type instead of an occurrence, hand-writing the derived TotalThickness, putting a length unit on an area quantity, and leaving IfcMaterialList in a new IFC4 file. Covers the Pset_ and Qto_ naming conventions, the NoRelatedTypeObject WHERE rule, the occurrence-only rule for material usage entities, derived attributes, quantity unit-type WHERE rules, and the IfcMaterialList legacy smell, across IFC2x3, IFC4 and IFC4.3. Keywords: property set error, Pset_ prefix, custom property set, IfcPropertySet, IfcRelDefinesByProperties, NoRelatedTypeObject, attach Pset to type, quantity set, IfcElementQuantity, Qto_ prefix, Ifc
    203 repo stars
  22. ▌
    Ifc Syntax Geometry Tessellation · impertio-studio bundle
    Use when you need to author, read, or debug tessellated (faceted) geometry in an IFC4 or IFC4.3 model : triangle meshes and polygon meshes built from a shared indexed point pool, the lightweight geometry that the Reference View MVD relies on. Prevents the tessellation errors that break meshes : 0-based instead of 1-based indices, a triangle row with the wrong number of indices, a PnIndex indirection applied twice, a Closed flag that lies about whether the mesh is a solid, and using tessellation entities in an IFC2x3 file where they do not exist. Covers IfcCartesianPointList3D and IfcCartesianPointList2D, IfcTessellatedFaceSet, IfcTriangulatedFaceSet (Coordinates, Normals, Closed, CoordIndex, PnIndex), IfcPolygonalFaceSet, IfcIndexedPolygonalFace, IfcIndexedPolygonalFaceWithVoids, the PnIndex indirection layer, the RepresentationType Tessellation mapping, and the IFC4 / IFC4.3 version differences. Keywords: IFC tessellation, IfcTriangulatedFaceSet, IfcPolygonalFaceSet, IfcTessellatedFaceSet, IfcCartesianPointL
    203 repo stars
  23. ▌
    Ifc Agents Migration Orchestrator · impertio-studio bundle
    Use when asked to migrate an IFC file to another schema version, upgrade an IFC2x3 model to IFC4 or IFC4.3, downgrade an IFC4 model, or plan a schema-version conversion of an IFC dataset end to end. Prevents copying attributes blindly across a version boundary, silently dropping non-migratable entities, downgrading when an upgrade was the real goal, confusing geometry conversion with schema migration, and declaring a migration done without revalidating the result. Covers the migration workflow as an orchestration : source-schema detection, direction choice, the two-stage entity-then-attribute remap, the non-migratable-entity ledger, the ifcpatch Migrate recipe, and post-migration validation, across IFC2x3, IFC4 and IFC4.3. Keywords: IFC version migration, migrate IFC file, upgrade IFC2x3 to IFC4, IFC4 to IFC4.3, downgrade IFC, schema conversion, ifcpatch Migrate recipe, entity map, attribute map, IfcWallStandardCase deprecated, IfcBuildingElement renamed IfcBuiltElement, IfcBuildingSystem IfcBuiltSystem, non-
    203 repo stars
  24. ▌
    Ifc Syntax Geometry Representations · impertio-studio bundle
    Use when you need to attach geometry to an IFC product, read a model's shape data, or debug why a representation is rejected : the product-to-shape chain, IfcShapeRepresentation, the RepresentationIdentifier and RepresentationType value tables, the Model representation context and its sub-contexts, topology representations, named shape aspects, and mapped (instanced) geometry. Prevents a shape representation with no placement, a non-shape-model entity inside IfcProductDefinitionShape, a missing or mismatched RepresentationType, a sub-context with literal instead of derived attributes, and a self-referential mapped item. Covers IfcProduct.Representation, IfcProductRepresentation, IfcProductDefinitionShape, IfcShapeRepresentation, IfcTopologyRepresentation, IfcGeometricRepresentationContext, IfcGeometricRepresentationSubContext, IfcGeometricProjectionEnum, IfcShapeAspect, IfcRepresentationMap, IfcMappedItem, IfcCartesianTransformationOperator, IfcRepresentationItem, and IFC2x3 / IFC4 / IFC4.3 version difference
    203 repo stars
  25. ▌
    Frappe Core API · impertio-studio bundle
    Use when building ERPNext/Frappe API integrations (v14/v15/v16) including REST API, RPC API, authentication, webhooks, and rate limiting. Covers external API calls, endpoint design, token/OAuth2/session authentication. Keywords: API integration, REST endpoint, webhook, token authentication,, how to connect, external API, send data to another system, API not working, 401 error. OAuth, frappe.call, external connection, rate limiting.
    203 repo stars
  26. ▌
    Frappe Ops Bench · impertio-studio bundle
    Use when running bench commands, managing sites, configuring multi-tenancy, or setting up domains. Prevents misconfigured bench environments, broken site routing, and DNS mismatches. Covers bench CLI commands, site creation, bench init, multi-tenancy setup, DNS-based routing, common-site-config. Keywords: bench, site, multi-tenancy, domains, bench init, bench new-site, bench setup, common_site_config, bench command not working, site setup, multi-tenant, domain routing, new site..
    203 repo stars
  27. ▌
    Frappe Ops Cloud · impertio-studio bundle
    Use when working with Frappe Cloud, Press API, provisioning sites, or managing benches on Frappe Cloud infrastructure. Prevents failed deployments from misconfigured cloud settings and API misuse. Covers Frappe Cloud dashboard, Press API, site provisioning, bench management, environment variables, cloud-specific limitations. Keywords: Frappe Cloud, Press, cloud API, site provisioning, bench management, FC, frappecloud, Frappe Cloud deploy, FC hosting, cloud setup, managed hosting..
    203 repo stars
  28. ▌
    Frappe Ops Backup · impertio-studio bundle
    Use when configuring backups, restoring sites, encrypting backup files, scheduling automated backups, or planning disaster recovery. Prevents data loss from missing backups, failed restores, and unencrypted sensitive data. Covers bench backup, bench restore, backup encryption, S3/remote storage, scheduled backups, disaster recovery procedures. Keywords: backup, restore, encryption, S3, scheduled backup, disaster recovery, bench backup, bench restore, how to backup, restore database, backup failed, data recovery, automated backup..
    203 repo stars
  29. ▌
    Frappe Core Cache · impertio-studio bundle
    Use when implementing Redis caching, cache invalidation, or distributed locking in Frappe. Prevents stale cache bugs, race conditions from missing locks, and memory bloat from unbounded cache keys. Covers frappe.cache(), @redis_cache decorator, cache.get_value/set_value, cache invalidation patterns, frappe.lock, TTL strategies. Keywords: cache, Redis, redis_cache, invalidation, locking, frappe.cache, get_value, set_value, TTL, distributed lock, data not refreshing, stale data, cache not clearing, Redis error, slow repeated queries..
    203 repo stars
  30. ▌
    Frappe Core Files · impertio-studio bundle
    Use when handling file uploads, attachments, private/public file access, or S3 storage configuration. Prevents broken file URLs, permission leaks on private files, and failed uploads from incorrect MIME handling. Covers File DocType, frappe.get_file, upload API, private vs public directories, S3 integration, file URL patterns, attach field types. Keywords: file, upload, attachment, File DocType, private, public, S3, file_url, get_file, attach, upload not working, file missing, broken file link, download file, image not showing, attachment error..
    203 repo stars
  31. ▌
    Frappe Core Utils · impertio-studio bundle
    Use when working with utility functions in Frappe v14-v16. Covers frappe.utils.* for date/time, number/money, string, validation, and file path operations. Prevents reinventing stdlib alternatives that break timezone awareness, locale formatting, or multi-tenancy. Keywords: frappe.utils, nowdate, flt, cint, fmt_money, getdate,, date calculation, format number, money format, validate email, how to calculate days between. add_days, date_diff, validate_email, pretty_date, get_files_path.
    203 repo stars
  32. ▌
    Frappe Impl Hooks · impertio-studio bundle
    Use when implementing hooks.py configurations in a Frappe custom app. Covers step-by-step workflows for doc_events, scheduler_events, override/extend_doctype_class, permission hooks, extend_bootinfo, fixtures, asset injection, website hooks, and doctype_js. Prevents broken transactions, missed migrations, and multi-app conflicts. Keywords: hooks.py, doc_events, scheduler_events, override doctype,, how to add hook, when to use doc_events, scheduler setup, override existing behavior. extend doctype class, permission hook, scheduler job, fixtures, doctype_js, extend_bootinfo, website hooks.
    203 repo stars
  33. ▌
    Frappe Impl Jinja · impertio-studio bundle
    Use when building Jinja templates in Frappe: Print Formats, Email Templates, Notification templates, Portal Pages, and custom Jinja methods. Covers template creation workflows, child table handling, conditional sections, styling, multi-language support, and debugging. Prevents N+1 queries, wrong formatting, and Report Print confusion. Keywords: create print format, email template, portal page, pdf, create print format, invoice template, email template, PDF layout, custom print. template, invoice template, jinja methods, notification template, web page template, print format styling.
    203 repo stars
  34. ▌
    Frappe Core Search · impertio-studio bundle
    Use when implementing search functionality in Frappe v14-v16. Covers link field search (search_link), global search, FullTextSearch (Whoosh), SQLiteSearch FTS5 [v15+], Awesomebar customization, search_fields configuration, custom search queries, and website search. Prevents common mistakes with missing search_fields and permission filtering. Keywords: search, search_link, global_search, FullTextSearch, Awesomebar,, search not finding, link field empty, autocomplete not working, global search missing results. search_fields, standard_queries, SQLiteSearch, FTS5, Whoosh.
    203 repo stars
  35. ▌
    Frappe Ops Upgrades · impertio-studio bundle
    Use when upgrading Frappe/ERPNext between major versions (v14 to v15, v15 to v16), troubleshooting failed migrations, or planning rollback. Prevents broken upgrades from skipped patches, incompatible customizations, and missing pre-upgrade checks. Covers version upgrade paths, bench update, migrate command, patch troubleshooting, rollback procedures, breaking changes per version. Keywords: upgrade, migration, v14, v15, v16, bench update, bench migrate, rollback, patches, breaking changes, update failed, bench update error, migration error, patches failing, rollback after upgrade..
    203 repo stars
  36. ▌
    Frappe Core Logging · impertio-studio bundle
    Use when implementing logging, error tracking, or monitoring in Frappe v14-v16. Covers frappe.logger() for file-based logging, frappe.log_error() for Error Log DocType entries, request logging, Sentry integration, and production logging patterns. Prevents common mistakes with print(), swapped log_error arguments, and sensitive data. Keywords: frappe.logger, log_error, Error Log, logging, Sentry,, where are the logs, how to log errors, error tracking, print not showing, production logs. monitor, request logging, error tracking, debug, production.
    203 repo stars
  37. ▌
    Frappe Errors API · impertio-studio bundle
    Use when debugging or handling API errors in Frappe/ERPNext v14/v15/v16. Prevents silent failures and wrong HTTP status codes in REST endpoints. Covers 401 Unauthorized (wrong token format, expired OAuth), 403 Forbidden (missing @whitelist, allow_guest needed), 404 Not Found (wrong endpoint URL), 417 Expectation Failed (validation via frappe.throw), 500 Internal Server Error, CORS issues, CSRF token missing/invalid, rate limit exceeded (429), file upload failures, JSON parse errors in request/response, webhook delivery failures, and timeout on long operations. Keywords: API error, 401, 403, 404, 417, 429, 500, CSRF, CORS, REST,, API call fails, 403 forbidden, CORS error, token expired, endpoint not found, webhook not received. whitelist, webhook, rate limit, file upload, authentication token.
    203 repo stars
  38. ▌
    Frappe Impl Reports · impertio-studio bundle
    Use when building Script Reports, Query Reports, dashboard charts, or Number Cards in ERPNext. Prevents empty report output from wrong column definitions, broken filters, and unoptimized SQL in large datasets. Covers Report Builder, Script Report (Python + JS), Query Report, Report filters, dashboard Chart DocType, Number Card, report permissions. Keywords: report, Script Report, Query Report, dashboard, chart, Number Card, filters, columns, execute, get_data, create report, custom report, dashboard chart, report empty, no data showing..
    203 repo stars
  39. ▌
    Frappe Impl Website · impertio-studio bundle
    Use when building portal pages, Web Forms, website routes, or configuring themes and SEO in Frappe. Prevents 404 errors from wrong route resolution, broken Web Form submissions, and missing meta tags for SEO. Covers Web Page, Web Form, Portal Settings, Website Settings, website routes, Jinja templates, Blog, Web Template, has_web_view, meta tags, sitemap. Keywords: website, portal, Web Form, Web Page, route, theme, SEO, meta tags, has_web_view, Blog, Web Template, sitemap, customer portal, self-service, public form, web page, website not showing, 404 on portal..
    203 repo stars
  40. ▌
    Frappe Core Database · impertio-studio bundle
    Use when performing database operations in ERPNext/Frappe v14-v16. Covers frappe.db methods, ORM patterns (frappe.get_doc, frappe.get_list), raw SQL, caching patterns, and performance optimization. Prevents common mistakes with database transactions and query building. Keywords: frappe.db, frappe.get_doc, database query, SQL, ORM, caching, database performance, query returns nothing, slow database, how to fetch data, get document by name, frappe.get_list empty.
    203 repo stars
  41. ▌
    Frappe Core Workflow · impertio-studio bundle
    Use when creating or modifying Frappe Workflows, defining states and transitions, adding action conditions, or troubleshooting workflow permission errors. Prevents stuck documents from misconfigured transitions, missing state permissions, and circular workflow paths. Covers Workflow DocType, workflow states, transitions, actions, conditions (Python expressions), workflow permissions, workflow_state field, Workflow Action DocType. Keywords: workflow, states, transitions, actions, conditions, workflow_state, Workflow Action, approval, document workflow, approval process, document stuck, cannot change status, workflow not moving, who can approve..
    203 repo stars
  42. ▌
    Frappe Impl Workflow · impertio-studio bundle
    Use when implementing document Workflows, approval chains, or state-based transitions in Frappe. Prevents stuck documents from missing transitions, broken approval chains, and permission errors on workflow actions. Covers Workflow DocType, Workflow State, Workflow Action, transition rules, allowed roles, conditions, workflow_state field, apply_workflow. Keywords: workflow, approval, transition, Workflow State, Workflow Action, state machine, approval chain, workflow_state, approval chain, document approval, multi-step approval, workflow stuck, status transitions..
    203 repo stars
  43. ▌
    Frappe Ops Deployment · impertio-studio bundle
    Use when deploying Frappe/ERPNext to production, configuring Nginx or Supervisor, setting up Docker, enabling SSL, or hardening security. Prevents insecure deployments, missing reverse proxy config, and broken process management. Covers production setup, Nginx configuration, Supervisor/systemd, Docker Compose, Let's Encrypt SSL, firewall rules, security hardening. Keywords: deployment, production, nginx, supervisor, docker, ssl, letsencrypt, security, gunicorn, systemd, go live, production setup, HTTPS setup, server config, deploy to VPS, Docker setup..
    203 repo stars
  44. ▌
    Frappe Errors Hooks · impertio-studio bundle
    Use when debugging hooks.py errors in Frappe/ERPNext. Covers hook not firing (typo, wrong dict structure), circular imports, app_include_js path errors, scheduler_events not running, doc_events on wrong DocType, permission_query_conditions SQL errors, override_doctype_class import failures, extend_doctype_class [v16+] conflicts, fixtures not loading. Error diagnosis by hook type for v14/v15/v16. Keywords: hooks.py error, hook not firing, scheduler not running,, hook not working, scheduler not running, app_include not loading, override not applied. doc_events error, circular import, fixtures error, override class error.
    203 repo stars
  45. ▌
    Frappe Impl Customapp · impertio-studio bundle
    Use when building a custom Frappe app from scratch. Covers bench new-app walkthrough, app structure decisions, adding DocTypes, hooks, patches, fixtures management, development workflow (bench migrate, build, clear-cache), testing, packaging, installing on another site, version management, and app dependencies for v14/v15/v16. Keywords: create custom app, new frappe app, bench new-app, app structure, module creation, doctype creation, fixtures, patches, deployment, packaging, data migration, patch file, patches.txt, migrate data between DocTypes, create new app from scratch.
    203 repo stars
  46. ▌
    Frappe Impl Scheduler · impertio-studio bundle
    Use when implementing scheduled tasks and background jobs in Frappe v14/v15/v16. Covers hooks.py scheduler_events, frappe.enqueue, queue selection, job deduplication, testing with bench execute/scheduler, monitoring via Scheduled Job Log and RQ Dashboard, error handling, long-running job patterns, email digest, data cleanup, and report generation. Keywords: schedule task, background job, cron job, async processing, queue selection, job deduplication, scheduler implementation, run task automatically, background process, scheduled task not running, async task.
    203 repo stars
  47. ▌
    Frappe Impl Workspace · impertio-studio bundle
    Use when creating or customizing Workspace pages in Frappe v14-v16. Covers Workspace DocType structure, shortcuts, number cards, dashboard charts, custom HTML blocks, JSON content format, shipping workspaces with custom apps, and role-based access control. Prevents common mistakes with content/child-table desync and missing fixtures. Keywords: workspace, desk, dashboard, number card, chart, shortcut,, customize desk, dashboard setup, add shortcut, module page, sidebar customize. workspace builder, module, fixtures, sidebar.
    203 repo stars
  48. ▌
    Frappe Ops Performance · impertio-studio bundle
    Use when tuning MariaDB, configuring Redis memory, sizing Gunicorn workers, setting up CDN, or profiling slow queries. Prevents performance bottlenecks from default configurations, memory exhaustion, and unoptimized database queries. Covers MariaDB tuning, Redis configuration, Gunicorn worker sizing, CDN setup, slow query log analysis, Python profiling, request profiling. Keywords: performance, MariaDB, Redis, Gunicorn, CDN, slow query, profiling, tuning, optimization, workers, slow page, loading time, ERPNext slow, why is it slow, page takes long, timeout..
    203 repo stars
  49. ▌
    Frappe Syntax Hooks · impertio-studio bundle
    Use when configuring Frappe hooks.py for app events, scheduler tasks, document events, fixtures, boot session, jenv customization, or website routing. Covers v14/v15/v16 including extend_doctype_class. Keywords: hooks.py, doc_events, scheduler_events, fixtures, app_include_js, override_whitelisted_methods, extend_doctype_class, hooks.py example, how to register hook, available hooks list, extend_doctype_class example.
    203 repo stars
  50. ▌
    Frappe Syntax Jinja · impertio-studio bundle
    Use when writing Jinja templates for ERPNext/Frappe Print Formats, Email Templates, and Portal Pages. Covers template syntax, context variables, filters, macros, and v16 Chrome PDF rendering. Prevents common mistakes with doc context and child table iteration. Keywords: Jinja, print format, email template, portal page, template syntax, PDF, v14-v16, template syntax, Jinja example, print format code, how to show child table in print.
    203 repo stars
  51. ▌
    Frappe Syntax Print · impertio-studio bundle
    Use when creating print formats or generating PDFs in Frappe v14-v16. Covers Jinja print formats, Print Designer [v15+], Letter Head, PDF generation API (get_pdf, download_pdf), Report print formats ({%= %} syntax), page breaks, and print CSS patterns. Prevents common mistakes with template engine confusion and PDF rendering. Keywords: print format, PDF, get_pdf, Jinja, Letter Head, print designer,, PDF not generating, print format broken, custom PDF, letter head, wkhtmltopdf error. wkhtmltopdf, WeasyPrint, page-break, download_pdf.
    203 repo stars
  52. ▌
    Frappe Testing Cicd · impertio-studio bundle
    Use when setting up CI/CD pipelines for Frappe apps, configuring GitHub Actions test workflows, or adding linting and security scanning. Prevents broken CI from incorrect test matrix configuration, missing MariaDB/Redis services, and uncaught code quality issues. Covers GitHub Actions workflows, test matrix (Python/Node versions), semgrep rules, pre-commit hooks, linting (ruff, eslint), CI test environment setup. Keywords: CI/CD, GitHub Actions, test matrix, semgrep, pre-commit, linting, ruff, eslint, continuous integration, automated tests, GitHub Actions, CI pipeline, pre-commit, code quality check..
    203 repo stars
  53. ▌
    Frappe Testing Unit · impertio-studio bundle
    Use when writing unit tests, integration tests, creating test fixtures, or running tests with bench run-tests. Prevents flaky tests from missing fixtures, incorrect test isolation, and wrong test base classes. Covers frappe.tests.utils, IntegrationTestCase, UnitTestCase, test fixtures, bench run-tests flags, test naming conventions. Keywords: unit test, integration test, IntegrationTestCase, fixtures, bench run-tests, frappe.tests, test_*.py, how to write test, test fixtures, run tests, test fails, bench run-tests example..
    203 repo stars
  54. ▌
    Frappe Agent Debugger · impertio-studio bundle
    Use when debugging Frappe errors, using bench console for live inspection, analyzing tracebacks, or reading Frappe log files. Prevents wasted debugging time from ignoring log context, misreading tracebacks, and not using bench console effectively. Covers bench console, frappe.logger, error log DocType, traceback analysis, common error patterns, log file locations, pdb/debugger integration, VS Code DAP, profiling, Frappe Recorder, mariadb diagnostics. Keywords: debug, bench console, traceback, error log, frappe.logger, pdb, debugging, log analysis, inspect, VS Code, DAP, profiling, recorder, mariadb, monitor, ERPNext error, how to debug, find the bug, what went wrong, stack trace, error message..
    203 repo stars
  55. ▌
    Frappe Agent Migrator · impertio-studio bundle
    Use when migrating a Frappe app between major versions, detecting breaking API changes, or resolving post-migration errors. Prevents failed migrations from undetected deprecated APIs, removed methods, and changed function signatures. Covers breaking change detection v14-v15-v16, deprecated API mapping, migration checklist, common migration errors, automatic fix suggestions. Keywords: migration, version upgrade, breaking changes, deprecated API, v14, v15, v16, migrate, compatibility, upgrade ERPNext, version change breaks, after update errors, deprecated method..
    203 repo stars
  56. ▌
    Frappe Core Permissions · impertio-studio bundle
    Use when implementing the Frappe/ERPNext permission system. Covers roles, user permissions, perm levels, data masking, and permission hooks for v14/v15/v16. Prevents common access control mistakes and security issues. Keywords: permissions, roles, user permissions, perm levels, data masking,, restrict records, who can see what, department access, row-level, user cannot see document, access denied. access control, security, has_permission.
    203 repo stars
  57. ▌
    Frappe Core Translation · impertio-studio bundle
    Use when implementing translations/i18n in Frappe v14-v16 apps. Covers _() in Python, __() in JavaScript, CSV translation files, bench commands, string extraction rules, lazy translation _lt(), PO/MO files [v15+], RTL support, and custom app translations. Prevents common mistakes with f-strings, concatenation, and template literals that break string extraction. Keywords: translation, i18n, _(), __(), _lt(), CSV, PO, gettext,, translate my app, multi-language, text not translated, wrong language, how to add translation. bench get-untranslated, RTL, localization.
    203 repo stars
  58. ▌
    Frappe Impl Controllers · impertio-studio bundle
    Use when building Document Controllers in a custom Frappe app: file creation, lifecycle hooks, validation, autoname, submittable workflows, controller override, child table controllers, flags system, migration from hooks.py and Server Scripts. Keywords: how to implement controller, which hook to use, validate vs on_update, override controller, submittable document, autoname, flags, extend_doctype_class, controller testing, child table controller, which hook to use, when does validate run, how to override save, document lifecycle.
    203 repo stars
  59. ▌
    Frappe Impl Whitelisted · impertio-studio bundle
    Use when building API endpoints with @frappe.whitelist() in Frappe. Covers endpoint design, permission patterns, error handling, client integration, file uploads, background jobs, rate limiting, REST API testing, and migration from Server Scripts to whitelisted methods. Prevents permission bypasses, SQL injection, and data exposure. Keywords: how to create API, build REST endpoint, frappe.call,, create API endpoint, call from frontend, custom API, REST endpoint, how to call python from JS. frappe.whitelist, API permission, guest API, secure endpoint, rate limiting, curl testing, frm.call.
    203 repo stars
  60. ▌
    Frappe Ops App Lifecycle · impertio-studio bundle
    Use when scaffolding a new Frappe app, configuring app settings, building assets, running tests, deploying, updating, or publishing to marketplace. Prevents broken app structure from incorrect scaffolding, missing setup.py fields, and failed builds. Covers bench new-app, app directory structure, setup.py/pyproject.toml, hooks.py config, bench build, bench run-tests, app publishing. Keywords: app lifecycle, new-app, scaffolding, setup.py, pyproject.toml, hooks.py, bench build, app publishing, marketplace, create app, publish app, app structure, how to start new app, app directory layout..
    203 repo stars
  61. ▌
    Frappe Syntax Reports · impertio-studio bundle
    Use when building Query Reports, Script Reports, or configuring Report Builder, including chart data integration. Prevents report errors from wrong column definitions, missing permissions, and incorrect data formatting. Covers Query Report (SQL-based), Script Report (Python-based), Report Builder, report columns definition, filters, chart_data, report permissions, prepared_report. Keywords: Query Report, Script Report, Report Builder, report columns, filters, chart_data, frappe.query_report, prepared_report, report columns, how to build report, report not showing data, chart in report..
    203 repo stars
  62. ▌
    Frappe Agent Architect · impertio-studio bundle
    Use when designing multi-app Frappe architectures, deciding whether to split functionality into separate apps, or implementing cross-app communication patterns. Prevents monolithic app sprawl, circular dependencies between apps, and broken override chains. Covers multi-app architecture decisions, app dependency management, cross-app hooks, override patterns, when to split vs extend, shared DocType strategies. Keywords: architecture, multi-app, app splitting, cross-app, dependencies, override, extend, monolith, modular, how to structure frappe apps, when to split apps, app design, multi-app planning..
    203 repo stars
  63. ▌
    Frappe Agent Validator · impertio-studio bundle
    Use when reviewing or validating Frappe/ERPNext code against best practices and common pitfalls. Checks generated code before deployment, validates against all 61 frappe-* skills, catches v16 patterns (extend_doctype_class, type annotations), validates ops patterns (bench commands, deployment), and generates correction reports. Keywords: review code, check script, validate deployment, find bugs, code quality, check my code, is this correct, code review, before deploying, best practices check.
    203 repo stars
  64. ▌
    Frappe Errors Database · impertio-studio bundle
    Use when handling database errors in Frappe/ERPNext. Covers DuplicateEntryError, LinkValidationError, MandatoryError, TimestampMismatchError, CharacterLengthExceededError, InReadOnlyMode, QueryTimeoutError, SQL injection errors, frappe.db.sql parameter format (% vs %s), get_value returning None, transaction deadlocks, MariaDB gone away, too many connections. Error-to-fix mapping for v14/v15/v16. Keywords: database error, DuplicateEntryError, TimestampMismatchError,, MariaDB error, MySQL error, column not found, table missing, duplicate entry, database crash. SQL injection, deadlock, MariaDB gone away, query timeout.
    203 repo stars
  65. ▌
    Frappe Impl Integrations · impertio-studio bundle
    Use when implementing OAuth providers, Connected Apps, Webhooks, Payment Gateways, or Data Import/Export in Frappe. Prevents authentication failures from wrong OAuth flow, missed webhook deliveries, and data corruption during bulk imports. Covers OAuth2 provider/client, Connected App DocType, Webhook DocType, Payment Gateway integration, Data Import, Data Export, frappe.integrations module. Keywords: OAuth, Connected App, Webhook, Payment Gateway, Data Import, Data Export, integration, API key, OAuth2, webhook trigger, connect to external service, OAuth setup, webhook configuration, import data, export data..
    203 repo stars
  66. ▌
    Frappe Ops Frontend Build · impertio-studio bundle
    Use when configuring frontend asset bundling, migrating from build.json (v14) to esbuild (v15+), or troubleshooting SCSS/CSS compilation. Prevents build failures from mixing v14 and v15 build systems and misconfigured asset pipelines. Covers esbuild configuration (v15+), build.json (v14), asset bundling, SCSS compilation, bundle.js setup, bench build flags. Keywords: esbuild, build.json, frontend build, SCSS, CSS, asset bundling, bench build, bundle.js, webpack, build error, assets not loading, CSS not updating, JS not compiling, bench build fails..
    203 repo stars
  67. ▌
    Frappe Ops Website Deploy · impertio-studio bundle
    Deploy HTML/CSS websites to ERPNext/Frappe (v15/v16) as Web Pages via the REST API. Use this skill whenever a user wants to host a website on ERPNext, deploy HTML mockups to Frappe, create Web Pages programmatically, configure Website Settings, or integrate Frappe's Discussion system as a forum. Also use when the user mentions "website on ERPNext", "Web Page API", "Page Builder", "Web Template", or wants to serve custom HTML from Frappe. Covers: Web Pages with Page Builder, custom Web Templates, Website Settings (navbar, footer), CSS management, Frappe Discussion integration, and deployment scripting.
    203 repo stars
  68. ▌
    Frappe Syntax Doctypes · impertio-studio bundle
    Use when creating or modifying DocType JSON definitions, choosing fieldtypes, configuring naming rules, adding child tables, or setting up tree structures. Prevents invalid DocType configurations from wrong fieldtype choices, broken naming rules, and misconfigured child table links. Covers DocType JSON schema, all fieldtypes and their properties, autoname/naming_rule patterns, child table (Table fieldtype), tree DocTypes, virtual DocTypes, Single DocTypes. Keywords: DocType, fieldtype, naming_rule, autoname, child table, tree, virtual DocType, Single, JSON definition, Custom Field, Customize Form, add field without code, hierarchy, tree view, field types list..
    203 repo stars
  69. ▌
    Frappe Core Notifications · impertio-studio bundle
    Use when implementing email notifications, system alerts, Assignment Rules, Auto Repeat, or ToDo items. Prevents misconfigured Email Accounts, broken notification templates, and silent delivery failures. Covers frappe.sendmail, Notification DocType, Email Account setup, Jinja email templates, Assignment Rules, Auto Repeat scheduling, ToDo API. Keywords: notification, email, sendmail, Email Account, Assignment Rule, Auto Repeat, ToDo, alert, template, notify on approval, email when status changes, alert, email not sending, notification not working..
    203 repo stars
  70. ▌
    Frappe Impl Clientscripts · impertio-studio bundle
    Use when implementing client-side form features in Frappe/ERPNext: field visibility, cascading filters, calculated fields, custom buttons, server calls, form validation, child table logic, debugging. Covers step-by-step workflows from Setup > Client Script through migration to custom app JS. Keywords: how to implement client script, form logic workflow, dynamic UI, calculate fields, frm.call, frappe.call, frappe.xcall, client script testing, field dependency, custom button, how to hide field, show field based on value, add button to form, calculate total, dynamic form.
    203 repo stars
  71. ▌
    Frappe Impl Serverscripts · impertio-studio bundle
    Use when implementing server-side features via Setup > Server Script: document validation, auto-fill, API endpoints, scheduled tasks, permission queries. Covers sandbox-safe coding, script type selection, testing, migration to controllers. Keywords: how to implement server script, which script type, sandbox limitation, Document Event, API script, Scheduler Event, Permission Query, migrate to controller, no-code automation, run code on save, auto-fill field, server-side validation, scheduled script.
    203 repo stars
  72. ▌
    Frappe Impl UI Components · impertio-studio bundle
    Use when building custom dialogs, extending List View, creating Page controllers, or adding Kanban/Calendar views and realtime updates. Prevents UI freezes from synchronous calls, broken dialogs from wrong field definitions, and missed socket events. Covers frappe.ui.Dialog, frappe.ui.form.MultiSelectDialog, List View customization, frappe.pages, Kanban Board, Calendar View, frappe.realtime, socket.io publish/subscribe. Keywords: Dialog, List View, Page, Kanban, Calendar, realtime, socket.io, frappe.ui, MultiSelectDialog, publish_realtime, popup dialog, custom dialog, list view customize, realtime update, live data, kanban setup..
    203 repo stars
  73. ▌
    Frappe Syntax Customapp · impertio-studio bundle
    Use when building Frappe custom apps from scratch. Covers app structure, pyproject.toml configuration, module creation, patches, and fixtures for v14/v15/v16. Prevents common mistakes with app scaffolding and module organization. Keywords: custom app, bench new-app, pyproject.toml, patches, fixtures, modules, app structure, app boilerplate, bench new-app example, module setup, patch example.
    203 repo stars
  74. ▌
    Frappe Syntax Scheduler · impertio-studio bundle
    Use when configuring scheduler events and background jobs in Frappe/ERPNext v14/v15/v16. Covers scheduler_events in hooks.py, frappe.enqueue() for async jobs, queue configuration, job deduplication, error handling, and monitoring. Keywords: scheduler, background job, cron, RQ worker, job queue, async task, frappe.enqueue, scheduled task, cron syntax, how often does it run, background job example, enqueue example.
    203 repo stars
  75. ▌
    Frappe Agent Interpreter · impertio-studio bundle
    Use when receiving vague or unclear ERPNext/Frappe development requests that need interpretation. Transforms requirements like 'make invoice auto-calculate' or 'add approval workflow' into concrete technical specifications. Determines which Frappe mechanisms to use and maps to the full 61-skill catalog. Keywords: vague requirement, clarify scope, translate business need, technical spec, implementation plan, what does this mean, unclear requirement, translate to code, how to build this.
    203 repo stars
  76. ▌
    Frappe Errors Controllers · impertio-studio bundle
    Use when debugging or preventing errors in Frappe Document Controllers. Prevents autoname failures, validate loops, on_submit without is_submittable, wrong lifecycle hook choice, get_list permission errors, NestedSet errors, extend_doctype_class conflicts, missing super() calls, and recursion without flags. Covers error diagnosis by lifecycle phase for v14/v15/v16. Keywords: controller error, autoname, validate loop, on_submit, is_submittable,, save fails, validate error, on_submit not working, autoname broken, controller crash. get_list, NestedSet, extend_doctype_class, super, flags, recursion guard.
    203 repo stars
  77. ▌
    Frappe Errors Permissions · impertio-studio bundle
    Use when debugging or handling permission errors in Frappe/ERPNext. Prevents broken document access from throwing in permission hooks. Covers PermissionError (403), has_permission hook failures, User Permission restricting too much or too little, perm_level blocking field access, System Manager bypass not working, Guest access denied, sharing permissions not applying, permission_query_conditions breaking get_list, owner-based permissions confusion, Apply User Permission checkbox behavior, and the permission debug workflow using frappe.permissions.get_doc_permissions. Keywords: PermissionError, has_permission, permission_query_conditions,, permission denied, cannot access, user blocked, sharing not working, role not enough. User Permission, perm_level, sharing, guest access, owner permission.
    203 repo stars
  78. ▌
    Frappe Syntax Controllers · impertio-studio bundle
    Use when writing Python Document Controllers for ERPNext/Frappe DocTypes. Covers lifecycle hooks (validate, on_update, on_submit), controller override, submittable documents, autoname patterns, UUID naming (v16), and the flags system. Keywords: document controller, lifecycle hook, validate, on_update, on_submit, autoname, naming series, flags, v14-v16, controller example, lifecycle hook order, when to use validate, Python DocType class.
    203 repo stars
  79. ▌
    Frappe Syntax Whitelisted · impertio-studio bundle
    Use when creating Frappe Whitelisted Methods (Python API endpoints) for v14/v15/v16. Covers @frappe.whitelist() decorator, frappe.call/frm.call invocations, permission checks, error handling, response formats, and client-server communication. Keywords: whitelisted, API endpoint, frappe.call, frm.call, REST API, @frappe.whitelist, allow_guest, API endpoint example, frappe.whitelist syntax, how to expose function.
    203 repo stars
  80. ▌
    Frappe Syntax Hooks Events · impertio-studio bundle
    Use when implementing document lifecycle hooks via doc_events in hooks.py, understanding event execution order, or extending/overriding document behavior from another app. Prevents silent hook failures from wrong event names, incorrect execution order assumptions, and broken override chains. Covers doc_events hook syntax, all document events (before_insert, validate, on_submit, etc.), event execution order, extend vs override behavior, cross-app doc_events. Keywords: doc_events, hooks.py, before_insert, validate, on_submit, on_cancel, lifecycle, document events, override, extend, event order, which event fires when, before_save vs validate, document event list..
    203 repo stars
  81. ▌
    Frappe Errors Clientscripts · impertio-studio bundle
    Use when debugging or preventing errors in Frappe Client Scripts. Prevents TypeError, frappe.call failures, async/await mistakes, cur_frm vs frm confusion, field not found, child table access errors, timing issues, CSRF token errors, and permission denied on frappe.call. Covers error diagnosis flowchart and debug tools for v14/v15/v16. Keywords: client script error, TypeError, frappe.call, async await,, Cannot read properties of undefined, TypeError, browser console error, script not running, form not updating. cur_frm, field not found, child table, CSRF, permission denied.
    203 repo stars
  82. ▌
    Frappe Errors Serverscripts · impertio-studio bundle
    Use when debugging or preventing errors in Frappe Server Scripts. Prevents ImportError (the #1 error), NameError for restricted builtins, sandbox violations, doc_events not firing, wrong script type selection, SQL injection, permission denied in scheduled scripts, infinite loops, and API scripts not returning JSON. Covers error message mapping table. Keywords: server script error, ImportError, NameError, sandbox,, ImportError in server script, script not running, sandbox error, restricted function. restricted, frappe.throw, doc_events, scheduler, API script, SQL injection.
    203 repo stars
  83. ▌
    Frappe Syntax Clientscripts · impertio-studio bundle
    Use when writing client-side JavaScript for ERPNext/Frappe form events, field manipulation, server calls, or child table handling in v14/v15/v16. Covers exact syntax for frappe.ui.form.on, frm methods, frappe.call, and browser-side validation. Keywords: client script, form event, frm, frappe.call, frappe.ui.form.on, JavaScript, UI interaction, field validation, form event syntax, how to write client script, frm example, frappe.call example.
    203 repo stars
  84. ▌
    Frappe Syntax Query Builder · impertio-studio bundle
    Use when building database queries with frappe.qb in Frappe v14-v16. Covers the PyPika-based query builder: SELECT, INSERT, UPDATE, DELETE, joins, aggregation, subqueries, cross-DB compatibility (MariaDB/PostgreSQL), and migration from raw SQL. Prevents SQL injection and DB-specific bugs. Keywords: frappe.qb, query builder, DocType, Field, pypika, join,, frappe.qb example, how to write query, join tables, SQL replacement, parameterized query. aggregate, ImportMapper, cross-database, parameterized query.
    203 repo stars
  85. ▌
    Frappe Syntax Serverscripts · impertio-studio bundle
    Use when writing Python code for ERPNext/Frappe Server Scripts including Document Events, API endpoints, Scheduler Events, and Permission Queries. Prevents the #1 AI mistake: using import statements in Server Scripts (sandbox blocks ALL imports). Covers frappe.* methods, event name mapping, and correct v14/v15/v16 syntax. Keywords: Server Script, frappe, ERPNext, sandbox, import, doc event, validate, on_submit, before_save, server script example, import not allowed, sandbox rules, which script type to use.
    203 repo stars
  86. ▌
    Blender Impl Addons · impertio-studio bundle
    Use when building a production Blender addon -- project structure, testing, CI/CD, or packaging for extensions.blender.org. Prevents the common mistake of hardcoding paths or skipping the extension manifest for Blender 4.2+. Covers multi-file addon structure, testing strategies, dependency management, and distribution workflows. Keywords: addon development, extension packaging, CI/CD, testing, multi-file addon, blender_manifest.toml, distribution, extensions.blender.org, how to make a Blender addon, publish addon, package addon.
    203 repo stars
  87. ▌
    Bonsai Impl Modeling · impertio-studio bundle
    Use when placing building elements (walls, slabs, columns, beams) in Bonsai or assigning IFC types and materials. Prevents the common mistake of creating geometry without assigning it to the spatial hierarchy (orphaned elements). Covers the complete element creation pipeline: type selection, geometric representation, material layer/profile/constituent assignment, and spatial containment. Keywords: wall, slab, column, beam, IfcWall, IfcSlab, IFC type, predefined type, material layer, material profile, spatial assignment, BIM modeling, make a wall, create building elements, add floor.
    203 repo stars
  88. ▌
    Ifcos Impl Mep · impertio-studio bundle
    Use when modeling MEP (Mechanical, Electrical, Plumbing) systems in IFC -- HVAC, piping, electrical circuits, distribution elements, ports, and connections. Prevents the common mistake of not creating ports for flow connections between elements. Covers IfcSystem, IfcDistributionElement, flow segments, fittings, and MEP property sets. Keywords: MEP, HVAC, piping, electrical, IfcSystem, IfcDistributionElement, port, connection, flow segment, fitting, mechanical, plumbing, duct, ventilation, connect pipes.
    203 repo stars
  89. ▌
    Blender Core Runtime · impertio-studio bundle
    Use when dealing with Blender Python runtime behavior -- mathutils, threading, handlers, timers, or crashes after undo/redo. Prevents the #1 runtime crash: using threading for bpy operations instead of bpy.app.timers, or caching bpy.data references across undo boundaries. Covers Vector/Matrix/Quaternion, KDTree, BVHTree, @persistent handlers, bpy.msgbus subscriptions, and background mode limitations. Keywords: mathutils, threading, undo, ReferenceError, bpy.app.timers, @persistent, bpy.msgbus, KDTree, BVHTree, background mode, Blender crash, startup script, auto-run, run on open, Blender freezes.
    203 repo stars
  90. ▌
    Ifcos Impl Cost · impertio-studio bundle
    Use when implementing cost estimation or 5D BIM workflows in IFC models -- cost schedules, cost items, cost values, or linking quantities to costs. Prevents the common mistake of creating cost items without linking them to element quantities. Covers ifcopenshell.api.cost module, cost schedules, cost values, and quantity-to-cost linkage. Keywords: cost, 5D BIM, cost schedule, cost item, cost value, quantity, ifcopenshell.api.cost, cost estimation, IfcCostSchedule, IfcCostItem, budget, pricing, bill of quantities.
    203 repo stars
  91. ▌
    Blender Core Versions · impertio-studio bundle
    Use when writing Blender Python code that must work across multiple versions (3.x/4.x/5.x), or when migrating scripts between Blender versions. Prevents breakage from renamed APIs, removed modules (bgl in 5.0), and changed function signatures. Provides the complete breaking changes matrix, deprecation timeline, and version-safe coding patterns. Keywords: Blender version, migration, deprecated, breaking change, bgl removal, bpy.app.version, version compatibility, 3.x, 4.x, 5.x, API changes, which Blender version, what changed in Blender 4.
    203 repo stars
  92. ▌
    Blender Errors Data · impertio-studio bundle
    Use when debugging Blender ReferenceError from removed objects, undo-invalidated bpy.data references, or stale ID pointers. Prevents the common crash of caching bpy.data references across undo/redo operations (references become invalid). Covers safe data access patterns, ID reference caching pitfalls, data lifecycle management, and bpy.data collections. Keywords: ReferenceError, undo, stale reference, bpy.data, ID pointer, data invalidation, removed object, data lifecycle, StructRNA, Blender crash, object disappeared after undo, StructRNA has been removed.
    203 repo stars
  93. ▌
    Blender Syntax Data · impertio-studio bundle
    Use when managing Blender data blocks -- collections, linked libraries, library overrides, or the asset system. Prevents the common mistake of not handling fake users when removing data blocks, or using append when link+override is needed. Covers bpy.data collections, BlendDataLibraries, library overrides, asset system, and data transfer between files. Keywords: bpy.data, collections, library overrides, linked library, asset system, append, link, fake user, data block, BlendDataLibraries, organize objects, link from other file, asset browser.
    203 repo stars
  94. ▌
    Blender Syntax Mesh · impertio-studio bundle
    Use when creating or editing mesh geometry in Blender Python -- vertices, edges, faces, BMesh operations, or bulk data access. Prevents the performance mistake of accessing vertices one-by-one instead of using foreach_get/foreach_set for bulk operations. Covers from_pydata, BMesh creation/editing, UV layers, vertex attributes, normals, and loops. Keywords: mesh, vertices, edges, faces, BMesh, from_pydata, foreach_get, foreach_set, UV layer, vertex colors, normals, bpy.types.Mesh, read vertex positions, edit mesh data, access face normals.
    203 repo stars
  95. ▌
    Bonsai Errors Common · impertio-studio bundle
    Use when debugging Bonsai errors -- IFC schema violations, spatial hierarchy errors, property set failures, geometry representation issues, or operator poll failures. Prevents wasting time on symptoms instead of root causes (e.g., missing IfcOwnerHistory in IFC2X3 causing cryptic errors). Provides diagnostic decision trees and recovery strategies for all common Bonsai failure modes. Keywords: Bonsai error, schema violation, spatial hierarchy error, poll failure, drawing error, BCF error, IFC error, troubleshooting, debug, Bonsai not working, Bonsai crashes, element not showing.
    203 repo stars
  96. ▌
    Blender Impl Animation · impertio-studio bundle
    Use when implementing AEC-specific animations -- construction sequences, camera walkthroughs, solar studies, or phasing visualizations in Blender. Prevents the common mistake of keyframing visibility instead of using proper collection visibility for construction phases. Covers NLA workflow orchestration, batch keyframe operations, and time-based visualizations. Keywords: construction animation, camera walkthrough, solar study, phasing, NLA, keyframe, construction sequence, visibility animation, AEC visualization, animate building, show build sequence, camera fly-through.
    203 repo stars
  97. ▌
    Blender Impl Operators · impertio-studio bundle
    Use when implementing complex Blender operators -- modal operators with timer callbacks, file browsers, batch processing, or multi-step workflows. Prevents the common mistake of blocking the UI thread in long operations instead of using modal + timer pattern. Covers modal operators, file browser integration, undo/redo support, progress reporting, and batch processing operators. Keywords: modal operator, timer callback, file browser, batch processing, progress reporting, undo support, multi-step workflow, INVOKE_DEFAULT, make custom button, add menu item, create toolbar button.
    203 repo stars
  98. ▌
    Blender Syntax Nodes · impertio-studio bundle
    Use when building node trees via Python -- Geometry Nodes, Shader Nodes, or Compositor Nodes. Prevents the breaking change of using node.inputs/outputs by index instead of NodeTreeInterface (4.0+) for node group I/O. Covers node creation, linking, group management, and the NodeTreeInterface API migration. Keywords: node tree, Geometry Nodes, Shader Nodes, Compositor, NodeTreeInterface, node_group, links, nodes.new, node sockets, procedural geometry, create nodes from Python, connect nodes, add node.
    203 repo stars
  99. ▌
    Bonsai Syntax Spatial · impertio-studio bundle
    Use when creating or managing IFC spatial hierarchy in Bonsai -- IfcSite, IfcBuilding, IfcBuildingStorey, IfcSpace, and their containment relationships. Prevents the critical mistake of not establishing proper spatial decomposition (IfcRelAggregates) causing elements to be invisible in model viewers. Covers spatial containment, decomposition, and Bonsai-specific spatial navigation tools. Keywords: spatial structure, IfcSite, IfcBuilding, IfcBuildingStorey, IfcSpace, IfcRelContainedInSpatialStructure, IfcRelAggregates, spatial hierarchy, add storey, create building structure.
    203 repo stars
  100. ▌
    Sverchok Syntax API · impertio-studio bundle
    Use when automating Sverchok from Python -- creating node trees programmatically, connecting sockets, setting parameters, or running batch parametric studies. Prevents the common mistake of not calling process_from_nodes() after modifying parameters (tree won't update). Covers node creation, socket connections, parameter sweeps, and batch processing. Keywords: Sverchok API, programmatic, node creation, socket connection, batch processing, parameter sweep, process_from_nodes, automation, Python scripting, create nodes from code, automate Sverchok.
    203 repo stars